J
Jennifer Crawford
I have a split database that I will be distributing to
four separate offices (both front and back). Since not
every office has access to the same shared drives, there
is nowhere I can put the backend so that the table links
will automatically know where the data is.
I tried copying the two databases to another computer to
test - in the hopes that it would realize that the table
link is incorrect and prompt the user to update this.
However all I get the following error:
"<filename> is not a valid path. Make sure that the path
name is spelled corectly and that you are connected to the
server on which the file resides"
The only options were OK or Help, neither of which allowed
me to update the link, and both of which shut down the
database so I can't even access Linked Table Manager to
try to fix it manually.
How can I fix this so that when I distribute this set of
databases they can actually be updated?
four separate offices (both front and back). Since not
every office has access to the same shared drives, there
is nowhere I can put the backend so that the table links
will automatically know where the data is.
I tried copying the two databases to another computer to
test - in the hopes that it would realize that the table
link is incorrect and prompt the user to update this.
However all I get the following error:
"<filename> is not a valid path. Make sure that the path
name is spelled corectly and that you are connected to the
server on which the file resides"
The only options were OK or Help, neither of which allowed
me to update the link, and both of which shut down the
database so I can't even access Linked Table Manager to
try to fix it manually.
How can I fix this so that when I distribute this set of
databases they can actually be updated?