backend file move problem

[judytjones]

Recently I used the Access 2007 Issues database template as a base for a
multi-user database and have trouble with the Issue table after a backend
split. When the backend data file is moved to a 2nd location, and tables are
re-linked, the Issue table continues to reference 'something' from the 1st
location.

After relinking, I get a message that all tables successfully relinked. And
ALL tables except for the Issues table relink fine. On hover, the Issues
table shows the new link location, but cannot open. The error message is
“Could not find file ‘ Z:\My Documents\previousLocation\Issues_be.accdb.’

Any ideas what ‘part’ of this table is still looking for the previous
location?

 

[Jerry Whittle]

Instead of relinking, delete the linked table that is giving you problems.
Then create a fresh, new link to it.

 

[judytjones]

yes, this does clear the problem; however...

the database that includes this table is for a children's home in a
'difficult' setting (in Honduras). The frontend has code that re-links the
fe to their LAN after I have added fe updates.

so with this code I would need to add
1- copy issue table from fe to LAN backend
2- set relationships to Issues table on LAN be (this table you will notice
has multi-relationships)
3- delete fe Issues table
4- link to be Issues table

I am willing to do this (if this is the best opt); but instead of 'working
around' the problem, was hoping to determine 'why' this is an issue to begin
with.

 

[BruceB]

Does your code refresh the front end database TableDefs collection
after you have relinked all the tables? If not, perhaps adding this
bit of code would solve the problem, e.g.

CurrentDb.TableDefs.Refresh

Bruce

 

[judytjones]

Thanks for your response.

I added your line of code,
CurrentDb.TableDefs.Refresh,
but still get the message "Could not find file ‘ Z:\My
Documents\previousLocation\Issues_be.accdb.’ Error #: 3024", so assuming the
error happens before reaching this new line of code.

Please also note that I cannot even relink the Issue table manually using
the Link Table Manager.
Linked Table manager sends an error of "Could not find file ‘ Z:\My
Documents\previousLocation\Issues_be.accdb.’"
All other tables can link successfully.

I take care of all install steps via code for ease of install for the end
user, so will need to code the steps mentioned previously; but of course
prefer to determine what is going on here and remedy the problem, so that I
can only use the standard re-link code.

 

[judytjones]

Please note that the reason I am unable to use my standard re-link code (or
even to re-link manually) in a database that includes the 2007 Issues
database, is because of a feature in the Issues database, ColumnHistory
function.

I found on a Microsoft forum that there's a bug that prevents tables
containing append-only memo fields from being re-linked.
The Issues Detail form keeps a history of the Comments field using
=ColumnHistory([RecordSource],"Comments","[ID]=" & Nz([ID],0))

Since I like this feature and want to keep it, I have decided to add code to
my Install auto re-links routine to repair the Issues table.

Anyone else come across a better option for working around this history
append field re-link problem?