On Sat, Apr 6, 2013 at 3:47 PM, AndyHC <[email protected]> wrote:
> mapped drives cause problems - use URIs > I think you mean UNCs. URIs are Uniform Resource Identifier, which really is uniform, as there are a set of industry-standard RFCs that define what they are ( http://en.wikipedia.org/wiki/Uniform_resource_identifier<http://en.wikipedia.org/wiki/Uniform_resource_identifier#Technical_view> provides a good overview) URIs include http:// and ftp:// and so forth. versus: UNC are Universal Naming Convention, which are Microsoft-only, and neither Universal nor a Convention. (Cite: http://en.wikipedia.org/wiki/Uniform_Naming_Convention#Uniform_Naming_Convention ) I have had more luck over the years with mapped drive letters. A number of our FoxPro projects use a drive letter and path stored in a preferences table for each workstation. Our most wide-spread VFP app tried to standardize on Drive F a long time ago, before the proliferation of local drives, and it was problematic. Sticking that setting in the table was the trick. What have been your experiences that make UNCs more desirable? --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4vkP=pajoexm8ap1uazgvhegwzy_fno3olwb31wjt-...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
