Moving backend database (with a strange issue)

[dslitteken]

I have successfully split our database. In changing the location of the backend (_be) database (using a copy), then re-linking in the frontend (_fe) to the new _be location, there is no issue. But if I rename the _be in the original location (which really should be deleted -- but glad I didn't yet), my front-end will not even come up (it shows the template page for new databases).

If I rename the _be database in the original location (which should not be involved anymore) to its correct name, the front end comes up, and all tables show they are still correctly pointing to the new location.

Hope this reads right. I need to know how the original _be database from which I copied for the move, could have any relationship to my _fe pointing to the new location.

This is all I need to be complete my split, since I will be moving the split database off my pc into a server environment, now that I have installed Bob Larson's tool to enable auto-updates (a great piece of work).

:banghead:Help!

 

[boblarson]

Double check, using the Linked Table Manager, that you have the correct location for all of the tables. You may have missed one when relinking.


You can also alternatively use this query:

SELECT MSysObjects.Database
FROM MSysObjects
GROUP BY MSysObjects.Database, MSysObjects.Type
HAVING (((MSysObjects.Type) In (4,6)));

which probably is easier.

 

[dslitteken]

Yes, I had a system table for Ribbon customization. You are a saint.
It's good to understand there was a real reason for this.

Thanks again for the Front End Auto Updating tool. Well done.

 

[boblarson]

Thanks again for the Front End Auto Updating tool. Well done.

Glad it is helpful. Amazingly enough I created it 7 years ago for someone at work (a large healthcare facility) so they could have individual frontends on each machine but not have a pain updating them all (they had been running off of one frontend for 120 people and having corruption issues constantly). So I then thought, why not share it freely. I've had a lot of people use it over that 7 years and from some very interesting companies and such. Even had someone from the U.S. Marine Corps using it in their official duties.