Same deal. llf's don't work, either. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lew Schwartz Sent: Friday, September 22, 2006 9:44 AM To: [EMAIL PROTECTED] Subject: RE: Preventing included filename resolution
Nope. The situation looks like this: Copy file <fullyqualifiedPath + filename> to <Newfullyqualified etc...> If <filename> is the name of a component included in the build, Fox tries to copy the path which existed at compile time + <filename> instead. It doesn't matter whether the build time path still exists at run time. I know this since I rename all my development directories when I'm testing prior to deployment to be sure everything needed by the build is actually in the app/exe. Guess I'll try ll file functions today. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roche Sent: Friday, September 22, 2006 9:14 AM To: [EMAIL PROTECTED] Subject: Re: Preventing included filename resolution On 9/21/06, Lew Schwartz <[EMAIL PROTECTED]> wrote: > I'm finishing an xcopy-like app and I notice that when adir() comes > across an external file has the same name as one of the component > files that has been included in the .exe, VFP tries to copy the > included name instead. I have fullpath on, but this doesn't resolve > the problem. Any ideas? Try specifying the full path to the file? -- Ted Roche Ted Roche & Associates, LLC http://www.tedroche.com [excessive quoting removed by server] _______________________________________________ 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 ** 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.
