Hi, we have an application that is written in VB6 and uses an Access
database at the back end.
In the last couple of months we have started to use Windows 2003 Server
with thin clients using Microsoft Terminal services. During testing our
latest release we have noticed a lot of clients getting 'locking'
errors.
The new release has altered 2 tables and the app opens 2 databases but
it is the un-altered database that has the most issues. Any ideas (I
have tried recreating the tables, converting the database to Access
2002 but we still get the errors).
Is there any easy way to detect why this is happening? (we also have
code to handle locking scenerio's with retries and time delays).
Unsure now if it is the environment using terminals or something to do
we Windows 2003 Server (in the VB App we use ADODB for connectivity).
PLEASE HELP...
database at the back end.
In the last couple of months we have started to use Windows 2003 Server
with thin clients using Microsoft Terminal services. During testing our
latest release we have noticed a lot of clients getting 'locking'
errors.
The new release has altered 2 tables and the app opens 2 databases but
it is the un-altered database that has the most issues. Any ideas (I
have tried recreating the tables, converting the database to Access
2002 but we still get the errors).
Is there any easy way to detect why this is happening? (we also have
code to handle locking scenerio's with retries and time delays).
Unsure now if it is the environment using terminals or something to do
we Windows 2003 Server (in the VB App we use ADODB for connectivity).
PLEASE HELP...