Ed,

I can definitely see the value of writing code that is free of any hard coded drive mappings, especially when writing code that is going to be comercially distributed. Using the registry or an INI file is definitley a slick way of doing this.

I do still however stick to my original point. That point being that a good network design implementation in most organizations should be able to have standards and continuity (regardless of how an app has been written that exists on that network). A good deal of VFP programmers (and again, not all) do most of their programming on custom Apps that exist on one particular network. Being able to count on a standard drive mapping scheme among the app's users should be a common, achievable practice.

Just because we can go to a lower common denominator (UNC pathnames) doesn't mean that we have to.