D
Dawg1998
My firm uses Access 97 for a custom-built accounting program. On
Windows 98 and Windows 2000 systems, the program works fine. However,
on Windows XP a new problem has cropped up.
Our app has a front end database and a backend database. Using some
custom code, we allow one user the ability to switch between two
different backend datbases with the same frontend.
On 98/2000, the system would close the previous backend and open the
new backend without issue. While a locked .ldb file would be open for
either frontend/backend connection, the lock was dropped for every
switch.
On XP, however, switching to another backend DOES NOT close the
previous .ldb connection and prevents returning to the first backend
without turning off the application. This problem renders the
application nearly worthless.
Does anyone have ideas about why XP does not release the locks on the
backend like 98/2000 does? How can I tell the File System to release
the locks if that is the issue?
Many thanks in advance.
Randal
Windows 98 and Windows 2000 systems, the program works fine. However,
on Windows XP a new problem has cropped up.
Our app has a front end database and a backend database. Using some
custom code, we allow one user the ability to switch between two
different backend datbases with the same frontend.
On 98/2000, the system would close the previous backend and open the
new backend without issue. While a locked .ldb file would be open for
either frontend/backend connection, the lock was dropped for every
switch.
On XP, however, switching to another backend DOES NOT close the
previous .ldb connection and prevents returning to the first backend
without turning off the application. This problem renders the
application nearly worthless.
Does anyone have ideas about why XP does not release the locks on the
backend like 98/2000 does? How can I tell the File System to release
the locks if that is the issue?
Many thanks in advance.
Randal