ironpen45
asked on
multiple mdb files created during terminal services session?
i have an mdb file which is the front to a sql server back end. a single copy resides on the local directory of a terminal services server, and it's the only copy of the mdb file that is being use for multiple TS users.
i now discovered that there are multiple mdb files that start with db1.mdb, db2.mdb, db3.mdb... up to six. i copied one of the files and inspected it, but couldn't open it with an error msg indicating that "the Msysdb" couldn't be found. so, i tried to view the tables (via import/linking) from another mdb file and all i found was system files.
are these multiple sessions of end-users using the same front end mdb?
i now discovered that there are multiple mdb files that start with db1.mdb, db2.mdb, db3.mdb... up to six. i copied one of the files and inspected it, but couldn't open it with an error msg indicating that "the Msysdb" couldn't be found. so, i tried to view the tables (via import/linking) from another mdb file and all i found was system files.
are these multiple sessions of end-users using the same front end mdb?
In a multi-user environment (I do the same thing on a TS) you need a copy of the GUI (not a shortcut) on each users' desktop. Is the db compacting on close?
ASKER
there's a single copy of the mdb. each TS account launches that same file. and yes the mdb file self compacts on close.
i tried to simulate multiple instances of the same mdb on my local machine. i opened it 3 times, and the file still remains, with its corresponding ldb. no other files were there.
i understand that a temporary mdb is created during the compacting process, but multiple instances and the fact that these don't disappear, that's a problem especially when several TS users are launching and shutting the file, cuz of drive space constraints.
any further thoughts?
i tried to simulate multiple instances of the same mdb on my local machine. i opened it 3 times, and the file still remains, with its corresponding ldb. no other files were there.
i understand that a temporary mdb is created during the compacting process, but multiple instances and the fact that these don't disappear, that's a problem especially when several TS users are launching and shutting the file, cuz of drive space constraints.
any further thoughts?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
my previous comment described how i had 3 instances of the same mdb. but only 1 temporary file appeared during the the closing of each file.
funny but the closing of the first and second instance was immediate while the third was slower, noting that actual compacting was occurring. if i'm simulating this as what would happen on the TS, could there be another factor involved?
funny but the closing of the first and second instance was immediate while the third was slower, noting that actual compacting was occurring. if i'm simulating this as what would happen on the TS, could there be another factor involved?