Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Odd / Incorrect FULLPATH return, depending
Message
From
02/03/2022 13:26:31
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
 
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Miscellaneous
Thread ID:
01683716
Message ID:
01683719
Views:
59
>> FULLPAT(UPPER(DEFAULTEXT(ALLTRIM(tcClassLibName), "VCX"))) returns the correct filespec from the command window, but from the EXE or debugger returns a constructed, NON-EXISTANT filespec that appears to be created based on the location of the executing EXE.

I've seen this when the exe cannot find the file on its search path. Past solution to detect included something along the lines of ...AND FILE(m.lcFullpathedFilename)
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us.
"
-- Shakespeare: Coriolanus, Act 1, scene 1
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform