On Tue, May 25, 2010 at 9:09 AM, Alan Bourke <[email protected]> wrote: > > > On Tue, 25 May 2010 08:14 -0500, "Stephen Russell" > <[email protected]> wrote: >> The worst lesson learned is that the drive letter location >> for that dbc is crucial. WTF ? How dare you bind in a drive letter >> to a location? How do I move stuff around as my network grows and >> changes over time? > > As far as I'm aware there are only relative paths in a DBC and the > backlink from the contained tables. The sensible thing is to always have > the DBC and associated DBF files etc in the same folder. You can then > move them around at will. In fact, as long as the relative paths stay > the same you can still move them around at will. Slightly clunky but > works. If the application is coded to look for data on a fixed path then > that's nothing to do with VFP per se. ----------------------
Sorry but I don't want my shipping guys to have any access to the real data in the accounting system. That and I don't want to give FedEx or UPS capability to harvest said data either. Thus you separate CONTAINER from data. All I want is a pointer to my real data for the shipping companies to use. -- Stephen Russell Sr. Production Systems Programmer CIMSgts 901.246-0159 cell _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** 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.
