Sharing database on network

[Kathy]

When I try to split a database to share on network
(a shared folder on my computer) the other users get a
message "(filename) isn't a vaild path. Make sure that the
path name is spelled correctly and that you are connected
to the server on which the file resides." They have not
problem when the database is not split. Would the fact
that both the frontend and backend database are in the same
folder have anything to with it? I want to split it so
that I can continue to update my forms and queries without
losing any info in the tables.

 

[Wayne Morgan]

When you split the database, give each user a copy of the front end on their
computer. This will cause you fewer problems. Link the tables in the
back-end using UNC, not mapped drives. This also will reduce your problems
because the UNC path ought to be the same for everyone. You can relink the
tables using the Linked Table Manager located under Tools|Database
Utilities|Linked Table Manager. Check the box that says "Always Prompt for
New Location" before clicking the Ok button. Either type in the UNC path
(\\computername\sharename\backend.mdb) or use Network Neighborhood to browse
for it.

 

[Kathy]

Thanks - will try this but am not quite sure what you
mean by UNC path -there is still a lot for me to learn in
Access. I looked it up in Help but still did not quit get
it - maybe when I get into it step by step I can figure it
out.

Thanks for the info.

 

[Steved]

make sure the database back-end is on a drive that you all
share.
You and the others must have the same mapping (drive
letter and path) for the linked tables to work.

The front-end is best at each local pc where the back-end
is at a "common" location.

Hope that helps

 

[Wayne Morgan]

UNC is Universal Naming Convention. When refering to a share over the
network, you can map a drive letter or just simple give the path to the
share. The latter is preferable because it tends to not move around. Mapped
drives tend to get set to whatever drive letter the user chooses.

A UNC path refers to the other computer by its name, the share name of the
shared directory on the computer, followed by any subdirectories and finally
the name of the file. The example I gave in my first message
(\\computername\sharename\backend.mdb) is a UNC path. It starts with two
back slashes, then the computer's name, a back slash, the share name, a back
slash, then the file name. If the file was located in a subdirectory under
the share, you would have to specify that as well. Essentially, the
\\computername replaces C:\, the rest is basically the same.

 

[Guest]

Thanks a million. That is what I needed. Now it works.

 

[andyrb]

UNC is Universal Naming Convention. When refering to a share over the
network, you can map a drive letter or just simple give the path to the
share. The latter is preferable because it tends to not move around. Mapped
drives tend to get set to whatever drive letter the user chooses.

A UNC path refers to the other computer by its name, the share name of the
shared directory on the computer, followed by any subdirectories and finally
the name of the file. The example I gave in my first message
(\\computername\sharename\backend.mdb) is a UNC path. It starts with two
back slashes, then the computer's name, a back slash, the share name, a back
slash, then the file name. If the file was located in a subdirectory under
the share, you would have to specify that as well. Essentially, the
\\computername replaces C:\, the rest is basically the same.