Link to home
Start Free TrialLog in
Avatar of tklingman
tklingman

asked on

Problem Launching a Fox Pro Application

I have an old VFP6 application which we will be replacing in about a year.  I have something like 15 users on Win7/32 bit machines that access this application from a windows 2003 server by clicking a shortcut to the application (within a mapped drive on their PCs) on the server.  A few weeks ago I had problems launching the program from my PC but I didn't have time to deal with it and other users did not report problems. (If I needed to use the program I would remote desktop into the server and use it their). Well, this morning a user reported the same problem I had and so I need to deal with this.  What happens is when I click the shortcut I get the following error messages: API library not found , (if I click OK I then get: ) File MSXBox does not exist; (if I click OK I then get: ) Variable MNDGL not found, (if I click OK I then get: ) Operator/Operand type mismatch.  I have full Admin rights to my computer and users have full rights to the application on the server.  Note: that only myself and this one other employee have this problem right now.  I've cleaned out my Windows Temp directory (not sure but thought it could not hurt). I have not idea what what would cause this problem and why only myself and this one other employee should have.
ASKER CERTIFIED SOLUTION
Avatar of Cyril Joudieh
Cyril Joudieh
Flag of Lebanon image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tklingman
tklingman

ASKER

Captain, this gave me enough information to kind of figure it out. I went to another user's computer which I knew was working correctly and looked at their shortcut and it was different than mine and the other employee's in that the location of the executable and start-in location had the syntax of the mapped directory to the program while mine had the syntax of a shared folder (not sure if this makes sense) on the server.  I reset mine (and the other employee's to syntax for the mapped directory and everything works correctly now.  What I don't understand is how the pathing on the shortcut could have changed - made no changes to it but even on the off chance I did, this other employee would have no idea how to do this, so I"m a bit puzzled.  But at least I know what to do if it should crop up again!  Thank you, Thank you!
This tells the operating system where the current folder is. It is obvious that the library files it was looking for are inside the folder of the application.
I thought that this might be the case, what's perplexing though is how the pathing on the shortcut for the employee and myself got changed, and I generally don't think these things happen on their own, so both of us must have done something and simply don't remember what that was.