This is somewhat outdated, but still a good read:

http://www.netinfoplus.com/mapmanager.htm


>>You might think it less than elegant to create a folder on the root of the "server" computer (e.g. \MyApp) just for your app (I'd agree :)).
>
>Yes, but it's what I'm doing now, anyway.
>
>>A compromise I've used in the past is to create a root folder called something like "NetShare", and make sure that all shared apps/data are installed to one or more subfolders of that (e.g. \NetShare\MyApp). That way you have a distinct separation between programs and data that are for local execution only, and those that may be executed locally or by other machines on the network. It can also simplify tasks such as backup.
>>
>
>That only makes sense when you have some control over the networks. In this case, it's a vertical market app, so all I can control is this application.
>
>>On a P2P network you don't have a system logon script available to map a drive letter to a network share. One way to achieve mostly the same thing is to create a batch file in a specific folder on every machine (including the "server") that gets run at the logon of any user:
>
>Does mapping buy anything that UNC paths don't give you?
>
>Tamar