11-23-2011 06:29 PM
I have run into an frustrating glitch in a multi-workstation automation system this week.
It comprises a dozen workstations controlling different processes, all logging into a MS-Access database on a separate workstation.
The system was originally written in Labview 7.11 with the old Datalogging and Supervisory Control and Database Connectivity toolkits.
I've been in the process of upgrading the old (and more frequently failing) WIndows XP/LV7.11 workstations and software to new Windows 7/LV2010 machines. Up until now the main difficulty was finding a stable way to bridge between the LabVIEW 7.11 DSCEngine tag data and the LabVIEW 2010 Shared Variable Engine data, a problem I solved last year.
I now want to move the database files to a new workstation. Since I am using ODBC with file-based DSN, pointing the connections at the new location seemed straightforward, and at first, it seemed to work just fine (a reminder, this is running with subvis developed with the old 7.1 Database Connectivity toolkit, recompiled in 32-bit Labview 2010 running in 64-bit W7), but I then realized that I was not getting fresh data back from the database file on the new workstation. I do get data back, but it's not current, and it persists even after rebooting the machine.
If I switch back to hosting the database file on an XP machine, everything works.
Any suggestions? Do I just need to get the new Database Connectivity module to connect to these files when hosted on a Windows 7 machine, or is there something more fundamental going on that has to be configured someplace else?
11-25-2011 03:10 AM
I've had several problems with Access on W7, mostly me not being able to select it as all. What i'd start with (unless you really need to file mobility) is to install a SQL Server (express) and import the data there. Set up a .udl pointing to the server (which'd be the same for 7.1 and 2010) and then try.
If it still doesn't work you probably have some Race condition in your old code that has risen with the recompile. Do the old code have lots of local variables?
I avoid the obvious "do you have database connectivity installed on the 2010 machine as i assume you do".
/Y