Do you know which library you are using and is not found
You may have to debug the EXE (can't use de**** step-by-step) by writing to a log or using Wait Window or MessageBox in strategic places, or debugout.
Once you find the offending API call you may have a handle on the problem.
Is this happening in the same PC
Which OS
Are there any permission problems
Are there any path problems
Is the user running the EXE the same user running the development APP in VFP (that is, are the credentials the same ) Sometimes you run an EXE through the scheduler which runs as a Windows user, not the logged in user.
It could be that the API call is in System32 and the user does not have sufficient access. Or maybe in another folder with the same problem.
Start by identifying the API call.
|