LabVIEW
Which file format for a complex configuration file?
@Frozen wrote:
"Use 1 Excel workbook..."
I chose this path. Not everyone is aware that Excel spread sheets can by accessed like a database.
However, my application only ever reads from the file and stores any HW specific info (COM ports, instrument address...) in an ini file.
No need for Excel to be installed on the deployment PC either.... unless of course you want to make changes to the file locally.
I thought I would update this with new information... I just found out that MS Excel does in fact need to be installed. I am not sure what version is required, but the "free" version is good enough.
@Frozen wrote:
@Frozen wrote:
"Use 1 Excel workbook..."
I chose this path. Not everyone is aware that Excel spread sheets can by accessed like a database.
However, my application only ever reads from the file and stores any HW specific info (COM ports, instrument address...) in an ini file.
No need for Excel to be installed on the deployment PC either.... unless of course you want to make changes to the file locally.I thought I would update this with new information... I just found out that MS Excel does in fact need to be installed. I am not sure what version is required, but the "free" version is good enough.
I have been running it without Excel. You need to install the database connection from Microsoft.
@mcduff wrote:
@Frozen wrote:
@Frozen wrote:
"Use 1 Excel workbook..."
I chose this path. Not everyone is aware that Excel spread sheets can by accessed like a database.
However, my application only ever reads from the file and stores any HW specific info (COM ports, instrument address...) in an ini file.
No need for Excel to be installed on the deployment PC either.... unless of course you want to make changes to the file locally.I thought I would update this with new information... I just found out that MS Excel does in fact need to be installed. I am not sure what version is required, but the "free" version is good enough.
I have been running it without Excel. You need to install the database connection from Microsoft.
Are you sure that you do not have Excel installed? That is what I thought too. Our CM recently re-imaged one of the test PCs and I was tasked with find out what was not working.
- reinstalled database connection drivers from MS - no change
- re-installed our test APP - no change
- Had CM install the free* version of Excel - test app works.
Conclusion: It needs Excel installed (or something that gets installed with Excel)
* Free version of Excel requires a credit card 🙃
@Frozen wrote:
@mcduff wrote:
@Frozen wrote:
@Frozen wrote:
"Use 1 Excel workbook..."
I chose this path. Not everyone is aware that Excel spread sheets can by accessed like a database.
However, my application only ever reads from the file and stores any HW specific info (COM ports, instrument address...) in an ini file.
No need for Excel to be installed on the deployment PC either.... unless of course you want to make changes to the file locally.I thought I would update this with new information... I just found out that MS Excel does in fact need to be installed. I am not sure what version is required, but the "free" version is good enough.
I have been running it without Excel. You need to install the database connection from Microsoft.
Are you sure that you do not have Excel installed? That is what I thought too. Our CM recently re-imaged one of the test PCs and I was tasked with find out what was not working.
- reinstalled database connection drivers from MS - no change
- re-installed our test APP - no change
- Had CM install the free* version of Excel - test app works.
Conclusion: It needs Excel installed (or something that gets installed with Excel)
* Free version of Excel requires a credit card 🙃
Just ran it now on a computer that has never had Excel, LabVIEW 2025Q3, .... (pause to build anticipation)
It works!
You need to install the dB component, which probably gets installed with Excel.
Look at this message.
@mcduff wrote:
@Frozen wrote:
@mcduff wrote:
@Frozen wrote:
@Frozen wrote:
"Use 1 Excel workbook..."
I chose this path. Not everyone is aware that Excel spread sheets can by accessed like a database.
However, my application only ever reads from the file and stores any HW specific info (COM ports, instrument address...) in an ini file.
No need for Excel to be installed on the deployment PC either.... unless of course you want to make changes to the file locally.I thought I would update this with new information... I just found out that MS Excel does in fact need to be installed. I am not sure what version is required, but the "free" version is good enough.
I have been running it without Excel. You need to install the database connection from Microsoft.
Are you sure that you do not have Excel installed? That is what I thought too. Our CM recently re-imaged one of the test PCs and I was tasked with find out what was not working.
- reinstalled database connection drivers from MS - no change
- re-installed our test APP - no change
- Had CM install the free* version of Excel - test app works.
Conclusion: It needs Excel installed (or something that gets installed with Excel)
* Free version of Excel requires a credit card 🙃
Just ran it now on a computer that has never had Excel, LabVIEW 2025Q3, .... (pause to build anticipation)
It works!
You need to install the dB component, which probably gets installed with Excel.
Look at this message.
From the link to the link...
"The Microsoft 365 Access Runtime enables you to distribute Access applications to users who don't have Microsoft Office installed on their computers or a version of Microsoft Office that doesn’t include Access. "
That is probably the missing part!
Now I just wish I had a computer (or VM) and the time to try it out on.
