Need to unlink 30 tables at once?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Access 2000 on local drive linked to Access 97 on server...Linked 30
tables...How do I break the link for all tables at one time.?
 
Manually, you delete each linked table one at a time.

Via VBA code, you loop through the linked tables via the TableDefs
collection in DBEngine(0).Databases(0) (or CurrentDb()) and delete them,
again one at a time.

What are you wanting to accomplish?
 
Thank you Ken.
I was trying to delete the links more quickly.
We are working on a 97 server version with 2003 on the desktop. He does not
want to update each time he opens the program.
 
You can use VBA code to relink the tables automatically when the database is
opened. Is that what you seek to do? If yes, post info regarding whether the
linking paths are changing from one session to another, or if the linking
paths remain the same and you just want to ensure that the front end and
back end are properly linked.
 
Ken

On a similar theme, I have an application that every time it is loaded, it
reads an INI file to determine the location of the backend DB and then
programtically closes all the links in the front end and re-creates them.
This all works fine, except for one client it is very sloooooow (typically
taking 2-3 minutes). I could work around this by checking if the current
linked path is as per the INI, but I have done this in the past and it hasn't
been this slow.

The backend resides on a PC (which is doubling as a server), which is
running XP Pro, Pentium 2.0GHz with 256MB Ram. It would seem to be a resource
issue (as if only one PC connects, this re-link process flies through, but as
soon as one PC is connected, then next user takes the time), but looking at
the minimum requirements for Access this would appear to be suitable. Is
there any other info you are aware of that I could look at to advise the
client on whether to upgrade memory, or PC or both and to what spec?
--

Many Thanks

Chris
 
soon as one PC is connected, then next user takes the time), but looking
at

When you have only one user connected, the network client
can actually cache the whole data file locally. Nothing has
to cross the network at all!

When you have two users, not only do all the database
commands have to go back to the 'server', you also have
to check the .LDB file to see if the other user is locking
the file or table.

But you can still make it much faster by Opening The First
Table after linking, and Holding It Open.

That way you don't have to look for the LDB file each time
and check the database locking (which takes most of the
time). You only have to check the table locking (which takes
much less time).

An yes, it depends which version of Access/Jet, which version
of Windows, and where the files are on your network.

(david)
 
Back
Top