Developer
Developer at UltraDNT.com
Fri May 7 09:57:19 CDT 2004
Linked Tabler Manager *WILL* show, and use, UNC if you go to Network Neighborhood first. It will NOT convert a mapped drive automatically. Can't say anything about your code w/o seeing it.<g> Steve -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mitsules, Mark S. (Newport News) Sent: Friday, May 07, 2004 10:45 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Linked Tables - UNC Path I was assuming that because the linked table manager visually shows the links with drive letters and NOT UNC naming then the links were actually hard coded to a particular drive letter. Are you saying that, by default, they are in fact utilizing UNC naming internally? Because, while perusing my modules I found one last instance where I'd neglected to use my constant (which uses UNC). Perhaps it was this last oversight that was giving me the "path not found" problem all along? Mark -----Original Message----- From: Gustav Brock [mailto:gustav at cactus.dk] Sent: Friday, May 07, 2004 10:32 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Linked Tables - UNC Path Hi Mark > Lol. I apologize...I think you're making the assumption that I have > existing relinking code already in place... Indeed, yes! > I don't:( This my first time at a TRULY multi-user app. Maybe I need > to be walked through this, but the built-in linked table manager > appears to use drive-letter mappings, not UNC. Follow the advice of Steve. > If I deploy the front-end to a person who doesn't have the same drive-letter > mappings, I get an error. > What I was looking for was an approach that > (1)mimics published relinking code, such as > http://www.mvps.org/access/tables/tbl0009.htm, > (2)forces UNC naming, yet > (3)doesn't include possible user intervention. That would be an "automatic" relinker but it wouldn't know where to find your backend except if you supply the (UNC) path within the application. If you relink using UNC path before deployment, this step should not be needed at all. /gustav > Hmmm .. I'm not sure I can follow you here - if you have the UNC path > it doesn't matter wether the user has a drive mapped to it or not. You > just need to relink with the UNC path. But why relink if you have > deployed the app linked to the UNC path of your choice? > /gustav >> Actually my situation is just the opposite. I know the remote server name, >> but the user may have that drive mapped to any letter. Therefore I >> would like to be able to relink automatically using UNC. I am not >> comfortable with the user manually choosing the location of the BE. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com