Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
COPY FILE bug?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00166255
Message ID:
00166327
Views:
13
>>Ah, leave the file there but call it from the destination dir? That's a good idea!
>>
>>As to the last bit, it's not internal to the exe.
>>
>>Thanks,
>>
>>-Michelle
>>
>>>Michelle,
>>>
>>>I'd to it like this:
>>>
>>>lcPath = set("path")
>>>lcDir = set( "directory" )
>>>set path to set(directory) + ";" + lcPath
>>>cd WhereYouWantTheNewDBC
>>>do tripsoft
>>>cd (lcDir)
>>>set path to (lcPath)
>>>
>>>COPY FILE may be choking on the fact that the .fxp is internal to the EXE and not a separate physical file.
>>>
>>>>Maybe there's a way aroung the bug. The tripsoft.fxp I'm copying is the program generated by gendbc. I need to copy it into the directory where I want the database to be generated. Is there some way to tell the program to do the database in a different directory than the one it's in?
>
>Hi Michelle,
>
>After following this a bit, I'm betting that your configuration either doesn't have a TMPFILES, etc. setting or if it does, it simply specifies C:. In these cases, compiled prgs are set to the window's temp file directory, during compilation. You might want to confirm whether or not the tripsoft.fxp actually exists in the temp directory. If not, it may be piicking up another file along the Fox path.
>
>hth,

It _doesn't_ exist in the temp directory. That's what it's complaining about. I don't understand why the COPY FILE command cares whether it's copying a compiled program or not. Why should that make a difference?

Thanks,

-Michelle
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform