Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Directory Confusion
Message
 
 
À
11/12/1998 15:03:07
Dragan Nedeljkovich (En ligne)
Now officially retired
Zrenjanin, Serbia
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Divers
Thread ID:
00166168
Message ID:
00166729
Vues:
17
>>>
>>>It may very well be just that. As soon as I get a minute I'm going to see if I can duplicate your problem and isolate a cause.
>>>
>>>Jason
>>
>>Good luck. It only does it for me on that one copy, not the other, and only in the exe.
>>
>>Thanks,
>>
>>-Michelle
>
>Michelle (-lly?),
>
>could it be that it finds the .fxp within the .exe only, when it actually doesn't exist in the directory? Check if the .fxp really exists there. I wouldn't be surprised if it doesn't - the File() function will still report .t. because it finds it in the .exe; you may fall into trouble with this (just like it seems you already did :). There were some ways of finding the real current directory where the .exe runs, I remember I had to play with sys(16), CurDir(), Set("dire") and FullPath() to achieve true reference to the current directory of the .exe, and not the directory where it was built in, or where the runtime is.
>
>Just try with a message box, show both variables with directories just before the copying takes place - you may be surprised.
>
>HTH

I did the mbox bit. The directories show up fine, and the fxp isn't part of the .exe. And it is in the directory, and it copies as it should. Just a wierd quirk, I guess. But it doesn't matter anymore since I no longer copy the file.

Thanks,

-Michelle
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform