Database Removing Links between mdb

[Guest]

I have two databases one (A) has core data and the tables are linked to the
2nd database (B). I then have an mde created from B. Since last week I have
been having trouble keeping the tables in A linked to database B. Both
databases reside in the same file and on the same server. Any suggestions on
how to prevent the loss of the links between the mdb files?

 

[Douglas J. Steele]

If the location of database B hasn't changed, there's no reason why you
should be experiencing any problems.

What are the symptoms of your "loss of the links"?

 

[Guest]

Each day the users log into the mde file but are now getting a message
letting them know that the database (B) can not find the linked tables. The
original programmer built a function to refresh the links so this may be
having a contributing effect; however there have been no changes to the
database except loading addtional data in the last 4-6 weeks. Once B is
relinked to A the users are fine for the day, however, once they log out for
the day and return the next day, the same error message reoccurs. This
error, from what I understand, has only occurred since last Tuesday. Prior
to that I am not aware the problem existed.

 

[Douglas J. Steele]

Sorry, without knowing what your relinking code is doing (and if there's any
code that "breaks" the links when the database closes), it's pretty hard to
offer suggestions.

Hopefully your application is split into a front-end (containing the
queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relationships). Each user should have his/her own
copy of the front-end (preferably on his/her hard drive). If that's the set
up you've got, does the problem occur for each front-end, or just certain
ones?

 

[Guest]

That is exactly the setup we have, a Front End and a Back End database. Each
user has a bat file that pulls down the mde onto their desktops when they
login. Currenly all of users are having the problem.

 

[Douglas J. Steele]

Does the copy on the server work correctly? If you're using a mapped drive,
does every user have the same mapped drive? If not, you may be better off
linking via a UNC, rather than the mapped drive. To do that, navigate to the
backend database through the Network Neighborhood (or whatever it's called
in the version of Windows you're using) rather than navigating through the
mapped drive.

 

[Guest]

The copy on the server does appear to be working correctly. I'm not certain
whether we are using a mapped drive or not, I will look at that as a possible
answer.

 

[Guest]

Here is the bat file that runs the app. It just references the frontend.
Should it also reference the backend?

Echo Off
Echo Now loading GPMA Application...
Echo Please standby...

copy \\greatplains\company\GP_App\GPMA_FrontEnd.mde
"%userprofile%\GPMA_FrontEnd.mde"

start "c:\Program Files\Microsoft Office\Office10\MSACCESS.EXE"
"%userprofile%\GPMA_FrontEnd.mde"

 

[Douglas J. Steele]

There's no reason for the bat file to reference the back-end.

How do you remap when the link is broken?

 

[Guest]

We go through network places, then click on the directories string until we
arrive at the mdb file. Click on the mdb and tell the system to "go" to
connect the tables.

 

[Douglas J. Steele]

Not clear to me whether you're using the Linked Table Manager or custom
code, but it sounds like custom code.

Afraid I have no other ideas.