Accessing FileMaker Pro DBs with LabVIEW ODBC

[chrisr]

I've seen numerous references but I'm unclear on how to access databases using ODBC through LabVIEW. I'm specifically interested in accessing FileMaker Pro databases on a Mac (LabVIEW is also on a Mac).

If anyone has any insight, I would greatly appreciate it.

Thanks

[Jeremy_L]

To access databases in LabVIEW, you can create a DSN for the ODBC driver. To do this, use OpenLink or Apple's ODBC Administrator. You can create either User or System DSNs and point them to the database you want to access. Then, in LabVIEW, when you're using the Database Connectivity Toolset, you can put down a string constant with the DSN name and wire that to the Open DB Connection.vi, which should then connect to the database. Hope this helps!

[chrisger]

hi there

under windows you can also use the microsoft ADO ActiveX control for accesing ODBC datasources. search the web for "LabSQL", its a free llb.

best regards
chris

[drval]

How about using the CD Connectivity Toolset tools/VIs?  I have a current app that uses those tools to access and MDB file.  I'm trying to work out how to do the same for FP8 files.  I give a Connection String to the Open Connection.VI -- what would the Connection String be for an FP8 file?

[drval]

Yet again a "sip of the flingers" -- I meant the DB Connectivity Toolset...

[tst]

Instead of building a connection string, you can create a DSN file as described earlier in the thread. This has some advantage because the connection information is stored in the file and you can easily change the file if you change the DB driver. You can do this in windows by going to the control panel>>Administrative Tools>>ODBC data sources and going to the File DSN tab. Once you save the file, you can wire the path of the file into the Open Connection VI. If you must build the connection string for your specific DB, you might want to search google for how to do this.

Also, don't post the same question to multiple threads. It will only make people waste their time and not want to help you the next time you ask.

[drval]

Sorry about the double posting.  I added a reply onto this current thread AFTER having started the other thread.  I'm having trouble navigating this new setup for the forums and frequenlty can't find information -- let alone find it easily.  I think I need to reset some of my access settings here as well.

It seems to me that whether I use the DSN file or Connection String approach that the real problem is actually setting the Connection string -- that's what's stored in the DSN file is it not?  And it seems like it's actually doing the correct Connection that is the problem.  If tried a number of things but just can't see to get it to work.

THe VI is the Connect_to_Database_by_name example, modified to use the new Connection String.

The information that I use for the Connection String is:

Provider=DataDirect 32-Bit SequeLink 5.4;
Data Source=C:\Program Files\Neurofeed\NeuroCarePro\Common Files\Users.FP8;
Persist Security Info=False

The error I get is:

Error -2146824582 occurred at DB Tools Open Connec (String).vi->Connect_to_DataBase_by_name Mine.vi

With the possible reason being:

Exception occured in ADODB.Connection, Provider cannot be found. It may not be properly installed.. Help Path is C:\WINDOWS\HELP\ADO270.CHM and context 1240655 in DB Tools Open Connec (String).vi->Connect_to_DataBase_by_name Mine.vi

But I believe that the correct ODBC driver is installed -- per FileMaker directions -- and is available via the System Administrator applet.

[tst]

A DSN file is an ASCII configuration file (you can open it with notepad) and it holds a bit more data than the connection string. The big advantage about using it is that windows builds it for you using a wizard, and often allows you to test the connection. If you managed to properly create a DSN file which works, then you will know that the problem is with your config file. If you haven't, then you probably have a problem with your driver.

As for the forum, for some inexplicable reason, the search defaults to the last 90 days. To search more, you actually need to go into the advanced search page.

[drval]

OK, thanks.  The wizard that you're describing is a Windows service -- not LV supplied?  Do I invoke that through the Administrative Services applet of Control Panels or, in some other way?

[tst]

Yes, it has nothing to do with LV and you start it by creating a new DSN file in the ODBC applet. The configuration screen vary depending on which driver you choose, so you might not have too many options with your own driver, but in any case, it should create a DSN file which you can use.