>>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.
>>
>
>What type of printer are they using? VFP has been known to have some problems with an HP driver from HP. This has also been known to cause other problems (graphics, etc.).

Larry

When I sent out the original applicaton, I had a few HP printer problems. Now, I always send out an application with the expr (except orientation line) and the two tag fields in the report table cleared out. Even doing that several HP Printers still gave me some problems which we were able to work around. I don't think the printer is a problem in this case since they are using the same printer for the other application. We had to send the original application out the first of the month to capture the monthend data from another system which proved to be quite a challenge, let alone the printer and install problems. No incremental roll out, it was all or nothing.


Thanks - I'll let you know how it worked.

Gaylen

>
>>
>>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.
>
>AFAIK, it doesn't use the registry at all so you should be okay using the default directory or SET PATH TO.