Links to tables are broken after I copy new frontend to clients

[jsccorps]

Have backend on server. Frontend copied to 10 clients. Worked fine until ...

I copied an updated frontend to the clients. Somehow, the links to the
backend were broken. To fix, I relinked the tables on each client to the
backend. (Must be a better way)

Is there a way to maintain the table links after I copy new frontends to the
clients?

 

[Sharkbyte]

I see this problem when the user's ODBC, or path, is different. Especially
if you are linking through a Networked drive.

Try setting your link up using My Network Places (Windows2000). This will
create the link with the true network path name. (ie.
\\ServerName\ShareName\Folder\DataDBFile)

HTH

Sharkbyte

 

[jahoobob]

Have backend on server. Frontend copied to 10 clients. Worked fine
until ...

I copied an updated frontend to the clients. Somehow, the links to
the
backend were broken. To fix, I relinked the tables on each client to
the
backend. (Must be a better way)

Is there a way to maintain the table links after I copy new frontends
to the
clients?

Place the Frontend on the server too. Then let each person shortcut to
the FE. You make changes in the one db and they all continue along.
They will need to close their shortcut and you will need to set them up
with appropriate security on the server that allows them to open the FE
at the same time.

 

[Rick Brandt]

Place the Frontend on the server too. Then let each person shortcut
to the FE. You make changes in the one db and they all continue
along. They will need to close their shortcut and you will need to
set them up with appropriate security on the server that allows them
to open the FE at the same time.

Terrible advice. Exactly the opposite of how a multi-user app should be set
up. Every user should have a separate (local) copy of the front end file.