01-11-2010 02:13 PM
01-12-2010 01:39 PM
Hi Gasson,
You might want to try posting to the Microsoft forums.
FLash
01-13-2010 01:24 AM
I have already read up on this and basically they say that Microsoft Jet 4.0 DB Provider is slowly being phased out. So this is why I was hoping to see if Labview maybe has another way to handle databasses?
Regards,
Gary
01-13-2010 09:31 AM
01-14-2010 12:40 PM
Hi Dennis,
One option would be to use UDL files. Would this be a valid alternative?
http://digital.ni.com/public.nsf/allkb/1D5EB4DCBD13106486256B9D005E11B0?OpenDocument
FLash
01-14-2010 12:51 PM
01-28-2010 11:36 PM - edited 01-28-2010 11:44 PM
Hi Gasson,
Have you tried connection string like "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=C:\myFolder\myAccess2007file.accdb;Persist Security Info=False;"
01-29-2010 12:08 AM - edited 01-29-2010 12:15 AM
It seems you are using mdb file, then you need to change the connection string. ACE represents MS 2007 Office System Driver, which may be what you are looking for.
From MSDN:
Instead of Microsoft Jet, Microsoft recommends using Microsoft SQL Server Express Edition or Microsoft SQL Server Compact Edition when developing new, non-Microsoft Access applications requiring a relational data store. These new or converted Jet applications can continue to use Jet with the intention of using Microsoft Office 2003 and earlier files (.mdb and .xls) for non-primary data storage. However, for these applications, you should plan to migrate from Jet to the 2007 Office System Driver. You can download the 2007 Office System Driver, which allows you to read from and write to pre-existing files in either Office 2003 (.mdb and .xls) or the Office 2007 (*.accdb, *.xlsm, *.xlsx and *.xlsb) file formats. IMPORTANT Please read the 2007 Office System End User License Agreement for specific usage limitations.