I can think about 2 reasons for such strange errors:
The APP has been buit with the VFP version that is different from the VFP version on the server. For example, APP is VFP7SP1 and VFP is VFP7RTM. Make sure that you're using the same VFP version in both cases.
The APP somehow got corrupted. Rebuilding it should fix the problem.
BTW, did you consider licensing implication of users running VFP? Each such user has to have VFP license in order to run it legally.
>We have a number of VFP 7 applications that are run using terminal server. The client recently upgraded the hardware on which these apps run, and we are now using Windows Server 2003. VFP 7 is installed on the server, so users can either run the apps from within VFP or by double-clicking the app in Windows Explorer. Until this most recent upgrade, it did not matter which way you started the apps. Recently, we have been experiencing some strange error messages. > >In one case, I traced the failure to the TEXT...ENDTEXT TO command failing to write anything to the variable. Again, this runs perfectly if you start VFP and then run the app, and it fails if you double click on the APP in explorer. If you build the app into a VFP EXE, there are no problems when you start it from the OS. > >I got an error message this morning about invalid number of parameters in ASCAN(), and, again, this only happens when you double click the app from Explorer. > >The obvious workaround is just to deliver everything as EXEs -- not a big deal. But I thought I would share the problem and see if anyone has determined a cause. Haven't had a chance to try this yet with 9. Thanks.
