"deiopajw" <g4****@hotmail.com> wrote in message
news:44**********************@news.optusnet.com.au ...
I have a Back end database on a network drive.
The copies of the front end are located on individual pc's (in their C
drive). The problem arises when a laptop user naturally hooks up to the
network but then the link from the front end (in the C drive of the
laptop)
to the back end (network drive) is lost. I have to then go to the tables
section of the database window of the Front End and remove the links then
link them again with the Back End. This at times happens with the pc's as
well. How can I prevent the re linking of the tables each time a laptop
user
hooks up to the network ???
I don't understand when this is happening. The only time you should need to
re-link is when the data source is moved. Of course, if a laptop opens the
front end application without a network cable in, then it won't be able to
find the data, but that is something you can check in your startup code and
should not require re-linking anyway.
If problems are being caused by different users using different drive
letters to refer to the backend folder, then you can re-link using UNC
naming eg rather than G:\Database\Data use \\MyServer\Shared\Database\Data .
If you really need to do the re-linking at runtime, then you can do it
quickly, automatically and without the knowledge of the user by writing a
bit of vba code. There must be hundreds of re-linking examples posted here
over the years.
