Splitting Data Base for Sharing

[Roger]

I have used the Splitter feature to split a data base and
end up with 2 files: The original with the tales linked
and another date base with _be added to the file name
(obviously the back end with just the tables).

I have shared the data base using the "Default Open Mode"
and when I run the front end from the remote computer it
opens to the main menu, but when I try to access for
example the data entry control, I get an error message
that says the "Path is not valid" to the file_be.mdb. I
have checked the path and it is correct. I obviously
need to something else. Any help please and thank you

Also, can the Front end remain on the server, as someimes
the data base is accessed from this computer also
Thanks again

 

[Arvin Meyer]

Make a backup copy of the front-end to stay on the server. Whenever possible
don't use your server as a workstation because it can cause your entire
operation to go down if you crash. Not only that, but it endangers your data
security. Even if you put a copy to be used on the server, make sure each
workstation has it's own copy.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access

 

[Guest]

Thanks for your advices. Can you also help me with the
error message that says it cannot find the file_be.mdb
which is on the server.
Thank you

 

[John Vinson]

Thanks for your advices. Can you also help me with the
error message that says it cannot find the file_be.mdb
which is on the server.

If the machine on which you are installing the frontend has a
different drive letter assigned to the server, you'll need to use
Tools... Database Utilities... Linked Table Manager to find the
backend. One useful solution is to navigate to the backend via
"Network Neighborhood" (or "My Network Places" or whatever it's called
on your machine) rather than to a drive letter; this will store a
connect string in \\server\path\filename form rather than in
D:/path/filename form, and as a result will not be affected when user
A calls the server their K: drive while user B calls it the Q: drive.

John W. Vinson[MVP]