How to read and write .mdb file in labview without having MS Access in the PC?

[rolfk]

ADO/DAO used to be all that was necessary to access mdb files. So using the database connectivity toolkit should simply work. You simply setup a DSN or maybe UDN pointing to that file and use that when opening a connection to the database with the database toolkit functions.

[PhillipBrooks]

---

rolfk wrote:
ADO/DAO used to be all that was necessary to access mdb files. So using the database connectivity toolkit should simply work. You simply setup a DSN or maybe UDN pointing to that file and use that when opening a connection to the database with the database toolkit functions.

---

I believe that the correct term is UDL (Universal Data Link). I only point it out because you won't find any anything googling 'udn'.

See this knowledgebase entry regarding creating a UDL file.

I've always used UDL files; I wrote my own ADO based libarary over 10 years ago.

After 7 ADO updates and three OS upgrades (NT, 2000, XP) it still works fine. Most of my ATEs don't have M-Office installed, only OpenOffice.

You can also use ADO to read and write MS-Excel files with the correct ADO options... 

 A UDL file contains ASCII text. There is a web site full of information about the options for various databases and file types. See www.connectionstrings.com

Message Edited by Phillip Brooks on 03-18-2010 07:04 AM

[rolfk]

Thanks for pointing that out. I wasn't entirely sure if I had the right spelling but felt to lazy to check it out. I for myself do never use UDL files but always either DSNs or direct connectivity strings to the open function. Also I'm not using any of the ADO based toolkits but my own ODBC API based VI library. Has the advantage to work on other systems than Windows when ODBC is available on them.

[RGreg]

Actually, while a UDL file is a text file, if you double click on it in WinXP or later you'll get a window popup similar to this:

You can use this tool to set specific options for the DB access (for example, password-only access).  And UDL files work regardless of whether you use the LV toolkit.  I've used UDL files with VB and scripts in other programs (like JMP or MATLAB).

[rolfk]

---

RGreg wrote:

And UDL files work regardless of whether you use the LV toolkit.  I've used UDL files with VB and scripts in other programs (like JMP or MATLAB).

---

So do DSNs and direct connection strings.