Arthur:

I agree.
Just that I'd like to know why sometimes :o)

Mal

>>I normally do not use PUBLIC, however, I did this once. I am still
>>not sure why I got the error messages but by moving the VFP runtimes
>>to the application folder the error message went away.
>>
>>Go figure. ????
>>
>>Mal
>
>
>Mal,
>
>Scientifically (I had to spell check that!), may I ask you:
>"What does the location of the VFP runtimes have to do with proper execution of code?"
>
>If the code works at ANY point when the VFP runtime is located in the application folder, and the code does not change, then Mister Spock would say the code IS FUNCTIONAL.
>
>If you do not change the code, but more the VFP runtime to a location which is otherwise perfectly acceptable, but the code fails, then scientific LOGIC must prevail.
>
>Scotty would say, "Don't change something that works laddie!"
>
>The fault must be somewhere else, perhaps in the mechanism that allocates Visual Foxpro global memory. Perhaps part of that mechanism is hardcoded to look for the runtime in the same folder?
>
>Yikkes!
>
>I mean, doesn't it make sense? Your code hasn't changed. If the code runs once, then the code must be good.
>
>This kind of stuff makes me crazy and amazes me at the same time.
>
>//Art