Link Table Manager Issue

  • Thread starter Thread starter Cathy
  • Start date Start date
C

Cathy

A drop down for "Manager" wasn't working on a form, so I checked the logic
and the table. The table showed the Manager ID in the Manager Name field,
and the Manager ID field was empty. (For the entire table.) This Access 2000
database is a split design, so I checked the back-end and the table was
correct. I repaired the link between the two database sections and the table
in the front end is now correct.

Any ideas on what could have caused this? Is there any way for me to
prevent it from happening in the future?

Thank you!
Cathy
 
Hi Cathy,

whenever you move the BE database to another directory -- or get a new
FE that was developed on another machine, you will have to re-link your
tables.

FE = Front-End
BE = Back-End


Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
(: have an awesome day :)
*
 
Is there anything else that could have cause it? Because as far as I know,
no one moved the FE...

Thanks!
Cathy
 
Hi Cathy,

the FE can move -- it is the BE that needs to stay in the same place --
or under a directory structure with the same name -- because Access is
expecting it to be in a specific place

c:\fullpath\database.mdb

If the path or filename of the BE gets changed, tables will need to be
re-linked


Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
(: have an awesome day :)
*
 
or for that matter, making any field changes directly in the backend.

I've seen wierd problems with linked tables that were only cured by deleting
the link in the frontend and using File... Get External Data... Link to relink
it. The Linked Table Manager just kept the same problems. It's a nuisance but
it's a fairly harmless and quick operation.
 
We eventually changed our code to delete-and-recreate
links by default instead of refreshing links by default because
of problems switching between ODBC and Jet, but for
me the specific problem caused by changing BE fields
had these specific characteristics:

Changing the last field in a table didn't matter.
No problem until the BE was compacted, perhaps weeks later.
The problem could be fixed by compacting the FE.

I theorise that compacting the BE has some effect on the
way changed fields are structured, and that compacting
the FE discards some of the table-link data.

(david)
 
We eventually changed our code to delete-and-recreate
links by default instead of refreshing links by default because
of problems switching between ODBC and Jet, but for
me the specific problem caused by changing BE fields
had these specific characteristics:

Changing the last field in a table didn't matter.
No problem until the BE was compacted, perhaps weeks later.
The problem could be fixed by compacting the FE.

I theorise that compacting the BE has some effect on the
way changed fields are structured, and that compacting
the FE discards some of the table-link data.
Click to expand...

Thanks, David. That's really an interesting result and makes more sense than
some of my speculations (I was ready to call in Ghostbusters!)

Filed for future reference.
 
Thank you all for your help and ideas!

Cathy

strive4peace said:
Hi Cathy,

the FE can move -- it is the BE that needs to stay in the same place --
or under a directory structure with the same name -- because Access is
expecting it to be in a specific place

c:\fullpath\database.mdb

If the path or filename of the BE gets changed, tables will need to be
re-linked


Warm Regards,
Crystal

remote programming and training

Access Basics
8-part free tutorial that covers essentials in Access
http://www.AccessMVP.com/strive4peace

*
(: have an awesome day :)
*
Click to expand...
 
Back
Top