setting up the network path for workstations

[magicdds-]

In the article "Splitting a access database, or how to run ms-access in a
multiuser mode" Albert D. Kallal states that you should not use drive letters
and mapping to link the front end of an application, on workstations, to the
backend on the server. Instead, use UNC as the path name.

My question is, if I put the front end of the application on a disk, to
distribute to users, how can I make it so the user can just copy the front
end .mde file to their computer, start up the application, and have the front
end link to the tables in the back end. How will it know the path, coming
from different workstations (or perhaps, using copies of the backend in
different companies servers, and each company has multiple workstations. How
will the backends know the path to that servers frontend)?

Also, how can I get an icon to appear on the desktop that will launch the
frontend, once it is installed on the workstation?

Thanks
Mark

 

[Tony Toews [MVP]]

In the article "Splitting a access database, or how to run ms-access in a
multiuser mode" Albert D. Kallal states that you should not use drive letters
and mapping to link the front end of an application, on workstations, to the
backend on the server. Instead, use UNC as the path name.

In my opinion using drive letters is fine so long as they are
consistent. That is all your users will be using Jointing to the
same server and share then that will work.

My question is, if I put the front end of the application on a disk, to
distribute to users, how can I make it so the user can just copy the front
end .mde file to their computer, start up the application, and have the front
end link to the tables in the back end. How will it know the path, coming
from different workstations (or perhaps, using copies of the backend in
different companies servers, and each company has multiple workstations. How
will the backends know the path to that servers frontend)?

That's exactly the problem. There is no good method currently in
existence for such.

Although once the user links the first time to the server, share, path
and file name I do save the settings in an INI file so they will be
used from then on. Or you could use the registry.

Also, how can I get an icon to appear on the desktop that will launch the
frontend, once it is installed on the workstation?

You'd have to set the shortcut icon properties using various API
calls.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/