To link a MS Access database as front-end to a MS Access data database as back-end in a network, we mormaly use the driveletter of the server and the name of the folder on this server to make the connection. In relation to that matter now and then i hear speaking of the use of an UNC to link to the server. The use of this UNC seems to have advantages compared to the conventional way of linking. If so, i can't understand why no book about MS Access, and i have a lot of them, don't say anything about that matter. Therfore i like to know if someone could give me somewhat more information about that UNC. I know what UNC means, but what i especialy want to know is how " IN PRACTICE" this UNC is determined in a network of computers each working with VISTA as O.S. Futhermore in what change the code that has to be written to realise the linking compared with the code for the conventional way of linking to the back-end.
Linking a front-end to a back-end using UNC
- Thread starter odrap
- Start date
HiTechCoach
Well-known member
- Local time
- Today, 17:21
- Joined
- Mar 6, 2006
- Messages
- 4,357
Nothing has to be changed in your database to use the UNC path. In my humble opinion, this really is a network management issue, not a Access/software programming issue and is beyond what Access programming books cover.
The advantage to the UNC path is the it will not change and is not depending on a mapped drive letter being mapped tot he correct resource ( a share on a computer).
In my opinion, this is also the disadvantage to using the UNC. If you move the data to a new resource ( a share on a computer), you must relink if using the UNC path sicne the path coputer part of the path has changes.. If you are using a mapped drive litter, thne all you have to do is remapp the drive letter tot he new resource.
In peer to peer networks, I like to use the UNC oath. This way I do not have to worry about mapped drives.
If I am using a domain and can run log on scripts to insure that the drive letters ad mapped correctly, then I will use a mapped drive letter and not the UNC.
All my databases are split it with the front end local. I use an auto updater so that the front end will get updated when the UNC path changes.
So in a stable environment where the back end is not moving locations, then the UNC path will be the best for support since there will not be any drive mapping issues.
The advantage to the UNC path is the it will not change and is not depending on a mapped drive letter being mapped tot he correct resource ( a share on a computer).
In my opinion, this is also the disadvantage to using the UNC. If you move the data to a new resource ( a share on a computer), you must relink if using the UNC path sicne the path coputer part of the path has changes.. If you are using a mapped drive litter, thne all you have to do is remapp the drive letter tot he new resource.
In peer to peer networks, I like to use the UNC oath. This way I do not have to worry about mapped drives.
If I am using a domain and can run log on scripts to insure that the drive letters ad mapped correctly, then I will use a mapped drive letter and not the UNC.
All my databases are split it with the front end local. I use an auto updater so that the front end will get updated when the UNC path changes.
So in a stable environment where the back end is not moving locations, then the UNC path will be the best for support since there will not be any drive mapping issues.
Last edited:
