LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

DBDisconnect disconnect all clients

Solved!
Go to solution

Dear forum experts,
I have developed an application which uses ODBC32 to access a MS Access database.
I was tell by someone that when the database is acceded by 2 ODBC clients on 2 different computers, if the first computer is shut down, the database connection is lost for the second one.
I first thought that MS Access was only a local database server, but reading the documentation, I have seen that it was really possible to be multi-clients.
Did someone have an explanation for the described behavior (second to connect is de-connected from database when first one is de-connected), Is there something missing in the DBConnection()? It may be more  a database problem that a labwindows Cvi one but I don't know how to handle this.
Best regards,
Serge

0 Kudos
Message 1 of 3
(1,362 Views)
Solution
Accepted by topic author Zergios26

Access is not a multiuser and not even a real remote database. While some drivers may support network transfer, the actual Access DB engine only supports a single client. Guaranteeing concurrent access to data doesn’t corrupt the data in the DB is a very difficult problem to solve. Access chose to avoid that problem by not allowing concurrent access!

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
Message 2 of 3
(1,320 Views)

Thank you for that comment.

0 Kudos
Message 3 of 3
(1,270 Views)