C
Chris W
Hi All
Okay - here is a puzzler for you clever people out there....
Configuration Details
Windows XP Pro SP2
Access 2003
FE/BE Configuration
BE - Access 2000 file format
FE - Access 2003 file format
FE/BE communicate via linked tables
Here is the problem
During the open event of the first form, all linked tables are deleted and
re-created
The form that is opened at launch creates a persistent connection to a table
T_System in the backend (i.e. the form is bound to a table)
The form is then hidden and a second form is opened up with a datasource of
T_System (same table)
I have a backup routine that does the following
1. cycles through the Forms collection in reverse order, closing all forms
down
2. when all forms are closed, a check is made to see whether there is a
locking file for the backend database
3. if there is - the backup aborts
Now for some reason, whenever I run this, after I have closed the forms
down, there is still a LDB file sitting out there. If I open the forms up
manually, and then close them, or even put them into design mode, the LDB
goes - which is what I would expect.
There is only me on the system during development.
Does anyone know what might be causing this, or where I could look to find
out more.
This backup code I have used in other projects and it works fine - the only
difference that I could see is that the second form in these cases is NOT
bound to a record source - but once it is closed, surely the connection goes?
Okay - here is a puzzler for you clever people out there....
Configuration Details
Windows XP Pro SP2
Access 2003
FE/BE Configuration
BE - Access 2000 file format
FE - Access 2003 file format
FE/BE communicate via linked tables
Here is the problem
During the open event of the first form, all linked tables are deleted and
re-created
The form that is opened at launch creates a persistent connection to a table
T_System in the backend (i.e. the form is bound to a table)
The form is then hidden and a second form is opened up with a datasource of
T_System (same table)
I have a backup routine that does the following
1. cycles through the Forms collection in reverse order, closing all forms
down
2. when all forms are closed, a check is made to see whether there is a
locking file for the backend database
3. if there is - the backup aborts
Now for some reason, whenever I run this, after I have closed the forms
down, there is still a LDB file sitting out there. If I open the forms up
manually, and then close them, or even put them into design mode, the LDB
goes - which is what I would expect.
There is only me on the system during development.
Does anyone know what might be causing this, or where I could look to find
out more.
This backup code I have used in other projects and it works fine - the only
difference that I could see is that the second form in these cases is NOT
bound to a record source - but once it is closed, surely the connection goes?