Larry -

I tested the application on five machines that had the sp4 run time and absolutely no problems. Been running several weeks in a production mode. I just sent the application out to another group which had the older run time version on their machines and I get a printing error and one of the forms isn't working correctly. I can't reproduce the error so I'm attributing them to the run time but I'm not really sure. I'm going to install a new run time on a few machines in the new group and try to resolve the problem.


Any idea if the exe program uses the registry first to find the run time files or does it search the current directory and then goes to the registry if it can't find them. If it goes to the registry first, my only solution appears to be to reinstall the run time for all locations. Although, I think I will volunteer to go to the Virgin Islands location to personally install the new runtime on that computer.


Thanks

Gaylen

>*snip*
>>Questions...
>>
>>When they click on the vfp exe file will it go out and try to use the old installed run time or will it look in its directory first for the run time files and use them?
>
>It looks in the current directory first and then out to the path. It is not linked in any way to any run-time files.
>
>>Does anyone know of any compatablilites problems or other issues doing it this way?
>
>AFAIK, you should have no problems.
>
>FWIW, I believe EXEs created using SP4 will still work using SP3 run-time files. You just won't get the bug fixes available. The same is true for all VFP 6 EXEs running on any of the SPs. For example, EXEs created with SP3 in mind that took advantage of the Session class could still run using SP2 or below. However, an error was thrown when a Session class was created, but not until then.