Confused about UNC usage

I am managing a database (written by someone else) that has pictures of
the members in the database stored on a hard drive.

The database keeps the path to the picture to display
(C:\Data\Access\Photos\{xxx}.jpg) in one of the columns. It works fine
(when the xxx is replaced with the member name of course) on that
computer.

But now, others on the network are wanting to use that database. So I
wanted to change the path to use the UNC path, but I must be confused
about something b/c it's not working.

I know the computer name is "99VDNTN", so I thought all I had to do was
change the "C:" to the name of the computer so the path now reads
"\\99VDNTN\data\access\photos\{xxx}.jpg".

But, even while on that computer, I can't go into Explorer and put
"\\99VDNTN\data\access\photos" (without the quotes of course) in the
address bar to go to the folder, because it tells me that "Windows
cannot find the path".

I haven't gotten to the point of other users trying to use it yet,
since I can't even get it to work on the local computer! But, the
entire drive is shared across the network, so I don't think a "share"
folder is going to be a problem.

Any thoughts?

The UNC will work from the computer that has the file or from the other
computers. The syntax for a UNC is

\\ServerName\ShareName\Subfolder\Subfolder\Filenam e.jpg

The subfolders would only be if needed. You will need to set up a file share
on the folder holding the pictures or one of the folders above it in the
directory tree. Sometimes there is a performance difference if your are
referring to the root folder of a share, so you may be better off sharing
the picture folder itself. You will need to give everyone read permissions
or better in the share and NTFS permissions for the folder.

--
Wayne Morgan
MS Access MVP


"Larry" wrote in message
oups.com...
I am managing a database (written by someone else) that has pictures of
the members in the database stored on a hard drive.

The database keeps the path to the picture to display
(C:\Data\Access\Photos\{xxx}.jpg) in one of the columns. It works fine
(when the xxx is replaced with the member name of course) on that
computer.

But now, others on the network are wanting to use that database. So I
wanted to change the path to use the UNC path, but I must be confused
about something b/c it's not working.

I know the computer name is "99VDNTN", so I thought all I had to do was
change the "C:" to the name of the computer so the path now reads
"\\99VDNTN\data\access\photos\{xxx}.jpg".

But, even while on that computer, I can't go into Explorer and put
"\\99VDNTN\data\access\photos" (without the quotes of course) in the
address bar to go to the folder, because it tells me that "Windows
cannot find the path".

I haven't gotten to the point of other users trying to use it yet,
since I can't even get it to work on the local computer! But, the
entire drive is shared across the network, so I don't think a "share"
folder is going to be a problem.

Any thoughts?

This is not the NG for this kind of question. This NG is about MS Access, a
database software.

Anyways, I can explain a little for you.

You cannot simply use computer name the replace "C:\" (or D:\, or E:\") in
local file path in UNC path.

UNC path is like \\ComputerName\SHARENAME\FoldersUnderneath\...

Say, on the computer, you share "C:\Data\Access\Photos" out and give this
share a name, called "MyPhotos", on the network, this shared location will
be \\ComputerName\MyPhotos, not \\ComputerName\Data\Access\Photos


"Larry" wrote in message
oups.com...
I am managing a database (written by someone else) that has pictures of
the members in the database stored on a hard drive.

The database keeps the path to the picture to display
(C:\Data\Access\Photos\{xxx}.jpg) in one of the columns. It works fine
(when the xxx is replaced with the member name of course) on that
computer.

But now, others on the network are wanting to use that database. So I
wanted to change the path to use the UNC path, but I must be confused
about something b/c it's not working.

I know the computer name is "99VDNTN", so I thought all I had to do was
change the "C:" to the name of the computer so the path now reads
"\\99VDNTN\data\access\photos\{xxx}.jpg".

But, even while on that computer, I can't go into Explorer and put
"\\99VDNTN\data\access\photos" (without the quotes of course) in the
address bar to go to the folder, because it tells me that "Windows
cannot find the path".

I haven't gotten to the point of other users trying to use it yet,
since I can't even get it to work on the local computer! But, the
entire drive is shared across the network, so I don't think a "share"
folder is going to be a problem.

Any thoughts?

You should those data files on a shared folder on the server.

Even while developing, you at some point should start using, and testing
things in the SAME environment as what you will deploy under.

I explain how to setup, and deploy ms-access in a multi-user environment
here. (and, I also mention UNC path names).

http://www.members.shaw.ca/AlbertKal...plit/index.htm

So, UNC path names is the way to go. (and, they "should" work even for a
local file, but suspect you don't have the folder shared correctly).


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.members.shaw.ca/AlbertKallal

Well, since this is all about a database storing the path of the
picturesin it, and having it accessed from other computers, and it is
an Access database (thus the path name \Data\Access\Photos), I figured
this would be a good place to put it.

Since the entire drive is shared, I figured that would be the same as
sharing the folder, it's just like sharing a folder higher up in the
tree, isn't it?

There is no "server" in this case, these are 3 computers in a church
and the Access database is on the computer used by the Main secretary.

Her entire drive is shared, so I thought that would be good enough and
would not need to directly share the photo folder.

I already had setup the reference to the back-end using the UNC path,
so everyone else in the office can use the front-end and still access
the back-end.

Ok, if that drive is fully shared,then it should work.

(as a side note, for virus stuff, you should actually only share the actual
folder, as sharing the root drive is bad for virus that spread on networks.
Sharing the full drive means that all of the juicy .exe files and dll files
are shared also....and that is not the best...


--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada

http://www.members.shaw.ca/AlbertKallal

Yes, there are some things that don't like to drill down to subfolders of a
shared drive, so if it doesn't work right, you can try sharing just the
folder the file is in to make it at the root of the share.

Also, even though you have set the Share permissions as needed and the root
of the share (in this case the root of the drive) may have the needed
permissions, if it is an NTFS format drive, it is possible to have different
permissions on the subfolder. Make sure both the Share and NTFS permissions
are as needed.

--
Wayne Morgan
MS Access MVP


"Larry" wrote in message
oups.com...
Since the entire drive is shared, I figured that would be the same as
sharing the folder, it's just like sharing a folder higher up in the
tree, isn't it?