09-30-2010 01:25 PM
Fellow wireworkers,
I have been using MS Jet to connect with an Access2003 database using the Database Connectivity toolkit for a few years now.
New project, LabVIEW2009, MS Office2010 (32bit) on Windows7 (64-bit).
Database Connectivity toolkit installed, example still uses Labview.mdb example database and MS Jet.
Installed the MS Access Database Engine 2010 Redistributable,
Set the connection string with the UDL file to "“Driver={Microsoft Access Driver (*.mdb, *.accdb)};DBQ=[path]\TestDatabase1.accdb" per instructions on the MS DBE 2010 site,
pressed the Build... button on the DataLink Properties wizard dialog,
Set the Machine Data Source to MS Access Database Type:User pressed OK and got this:
10-01-2010 05:48 PM
Hello,
Have you been successful creating this file in the Windows 7 environment? Drastic changes to User Account Controls (introduced in Vista) have been refined in 7, and limited the type of programmatic operations that are allowed by non-administrator processes. Can you verify that the process of creating the UDL is running as an administrator? Are you creating the UDL directly from renaming a text file, or are you creating the UDL using LabVIEW's tools menu? Does running the LabVIEW process (Right-Click "Run As Administrator") and creating the UDL with the LabVIEW tools menu allow the operation to complete correctly?
This entire set of steps may be moot; however, this would be my initial thought. Hopefully you may not have tried this configuration process. Please post any further questions.
Cheers,
Patrick Corcoran
Application Engineering Specialist | Control
National Instruments
10-01-2010 06:53 PM
Hi Patrick,
No... I have not tried your solution. I did us the old method of renaming the text file extension.
I will give this a try on Monday when back in the lab.
Thanks!
-Bill =]
10-04-2010 11:36 AM
Hi Patrick,
Thanks again for the quick reply.
I am using LabVIEW2009 Service Pack 1 (9.0.1 32-bit) on Win7 Enterprise
Intel Core2 Duo - 3GHz, 4 GB RAM 64-bit OS
After I launch LabVIEW2009 from the start menu either regular or Run as administrator, I select Tools|Create Data Link... and get the Data Link Properties dialog below:
but the window is frozen... I get the Windows "Ding (Beep?)" sound when I click anywhere on this dialog box.
The dialog appears above the Getting Started window, so I can close the Getting Started Window using the X close control, and then the application displays the following window above the frozen dialog:
I can move this window, but clicking on the close control does nothing...
I can close LabVIEW2009 by selecting "Close all windows" from the LabVIEW button on the task bar.
Any thoughts?
Thanks!
-Bill =]
10-04-2010 06:59 PM
Are you sure that Microsoft is still supporting jet on the 64 bit version? I recollect seeing somewhere that they stopped and do not provide the ODBC driver. The dialog window you show has nothing to do with LabVIEW. I would suggest the ms forums.
10-04-2010 07:31 PM
Hi Dennis,
Yes... you are correct. I also read that Win7 is not supporting JET... the solution I use under Windows XP.
I'll troll through the MS forums and see if they have anything.
I'm a bit surprised to not find many entries about MS Access and LabVIEW here, as I believe JET server support was dropped with the release of Vista.
Perhaps it "just works" and the installation I am working with is just goofy...
-Bill =]
10-04-2010 07:53 PM - edited 10-04-2010 07:54 PM
From: http://msdn.microsoft.com/en-us/library/cc280478.aspx
On a 64-bit computer, you must run packages that connect to Microsoft Access data sources in 32-bit mode. Both the Microsoft Jet OLE DB Provider and the OLE DB provider for the Microsoft Office 12.0 Access Database Engine are only available in 32-bit versions. |
hmmm... I don't know enough about 64-bit Win7 (running MS Office 2010 32-bit). Will need to dig a bit deeper, but as Dennis suggests, my problem could be with Microsoft not LabVIEW.
...Just tried launching the UDL dialog on my 32-bit Win7 laptop running LabVIEW9.0.1(32-bit) and get the identical error (freeze).
When I launch the UDL dialog on my 32-bit Win7 laptop running LabVIEW10.0(32-bit), the UDL dialog works correctly.
Both attempts are after running LabVIEW "as administrator".
I also noticed the LabVIEW10.0 UDL launcher does not flash the "Create Data Link" helper vi that displays an "Initializing" progress bar.
It still could be a Win7 32/64 bit thing, but LabVIEW10.0 works while LabVIW9.0.1 freezes the UDL dialog...
...and yes... my University lab is managed by IT and they have not yet deployed LabVIEW2010 as the upgrade was received too close to the start of the fall semester.
I'll keep digging, but any suggestions would be greatly appreciated....
-Bill =]
10-04-2010 09:39 PM
My suggestion would be to move to SQL Server Express.