Copying a database for use in another facility

[Mike Jakes]

I created a database and installed on our local server. I made a copy of the
existing database, then modified some of the tables for an application at
another of our facilities. I verified the new version was working properly,
etc. So far so good.

However, when I emailed the updated version to my counterpart in our other
facility and he attempted to install on the local server there, he was unable
to split the database and create a _be database. In fact, he was unable to
open the file at all as it was looking for the original path that the parent
database was located. I cannot figure out how to get around this. Recently
we installed the same database at another of our facilities with no issues
like this at all.

Any suggestions?

 

[John W. Vinson]

I created a database and installed on our local server. I made a copy of the
existing database, then modified some of the tables for an application at
another of our facilities. I verified the new version was working properly,
etc. So far so good.

However, when I emailed the updated version to my counterpart in our other
facility and he attempted to install on the local server there, he was unable
to split the database and create a _be database. In fact, he was unable to
open the file at all as it was looking for the original path that the parent
database was located. I cannot figure out how to get around this. Recently
we installed the same database at another of our facilities with no issues
like this at all.

Any suggestions?

Did you send them both the frontend and the backend? The frontend is not much
use unless it's linked to a (local to the network!!) backend, since that's
where the tables and the data reside.

It sounds like you might have just send the frontend!

If not, your colleague can probably use Tools... Database Utilities... Linked
Table Manager to link to the location of the backend on their network (so it
won't be futilely looking for a location which exists only on YOUR network).