F
FlyGuy
We have an Access 2002 application product that uses front end clients and
(linked) back end mdb data file. The back end data file is password protected.
The client has a Switchboard form that contains a combo box with "User"
names. The Switchboard is the startup form displayed after the DB is opened.
If we use the combo box to make any selection (other than the initial
default value), the back end LDB file appears and is never deleted again
unless the Switchboard and/or the client application is closed. This happens
even if no other user forms (other than the Switchboard) are open.
We have an"After Update" action on the combo box; even if this is removed,
the problem with the LDB file persists. It seems that any use of the combo
box causes the problem.
Note. The LDB file is not there immediately after the Switchboard first
opens; the combo box's initial value is initially set by the Switchboard's
"On Open" action.
We did not see this behavior when the backend MDB file was not password
protected!!!
The persistent LDB file is preventing us from using an internal utility that
backs up & compacts the back end (assuming no other active users). This
utility is called by a Switchboard button.
Again, this utility worked fine before we password protected the back end.
Can anyone advise what is going one here??
Is there any way we can clear the LDB other than by closing the Switchboard??
(linked) back end mdb data file. The back end data file is password protected.
The client has a Switchboard form that contains a combo box with "User"
names. The Switchboard is the startup form displayed after the DB is opened.
If we use the combo box to make any selection (other than the initial
default value), the back end LDB file appears and is never deleted again
unless the Switchboard and/or the client application is closed. This happens
even if no other user forms (other than the Switchboard) are open.
We have an"After Update" action on the combo box; even if this is removed,
the problem with the LDB file persists. It seems that any use of the combo
box causes the problem.
Note. The LDB file is not there immediately after the Switchboard first
opens; the combo box's initial value is initially set by the Switchboard's
"On Open" action.
We did not see this behavior when the backend MDB file was not password
protected!!!
The persistent LDB file is preventing us from using an internal utility that
backs up & compacts the back end (assuming no other active users). This
utility is called by a Switchboard button.
Again, this utility worked fine before we password protected the back end.
Can anyone advise what is going one here??
Is there any way we can clear the LDB other than by closing the Switchboard??