Error 673492112 occurred SQLSetConnectAttr failed

[RichBurb]

I get the following error occasionally.

Error 673492112 occurred.

Description:

Connect - [Microsoft][ODBC Microsoft Access Driver] The database has been placed in a state by an unknown user that preventes it from being opened or locked.[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

We are running an application simultaneously on several machines, so I am guessing that there may be a collision issue for the SQL access of a Microsoft Access Database. The calls area simple data requests, so I assumed that the server would handle the traffic.

Any help is appreciated.

[Dennis_Knutson]

I used to get this error too. Back when I was waiting for IS to finish installation of a large database system, the developer was using Access to do the design and then planned to move everything to SQL Server. If I remember correctly, the problem was that the Jet database that Access uses does page locking and not record locking. Several things were attempted to get around this basic limitation but none of them really worked 100% of the time. All problems disappeared when the SQL Server database was brought on line. I am not an Access expert by any means but I will never use a shared Access database again. SQL Server is not cheap but maybe you want to look at the open source MySQL. You can probably use your SQL commands in LabVIEW without any modification and if you want, you can still use Access as a front end to run queries and create reports.

[JQ]

i agree with dennis, MS Access is really not recommended... but as for whether it works well with LabVIEW or not, I cant say anything because I'm not a LabVIEW guru or what so ever... as for my experience with MYSQL (i've used it with java programmes), I personally recommend it if you want something that is free with reliable basic function.. if you are willing to spend, use MS SQL which have more functions and of cause not cheap...

[RichBurb]

Thanks for the tip. We have tried the SQL server and it seems to work, though we have not tested it over any great period of time.

Hopefully, this will give us the reliability we need.