>>>>Has anyone ever had a problem with an EXE created and compiled in Win95 behaving badly in Win 3.1? Both my development and test PCs are running Win95, and this VFP 3.0 app is working fine. When I install it on the client's Win 3.1 machines, I get errors like:
>>>>
>>>>"form C:\UDCAPP\UDCIN\HTCREPORT does not exist"
>>>>
>>>>I answer, "Well, of course it doesn't, that's the form name, you nincompoop." It doesn't react.
>>>>
>>>>I thought I had missed a form in my project, but I had tested it on my separate testing PC before installing it over there. I rebuilt, re-installed on the test PC, tested, every thing was fine. Take it back to client, nfg.
>>>>
>>>>Clues?
>>>
>>>Are you sure you don't have anything above 8.3 naming? Like if that htcreport is an scx, it's too long.
>>
>>DingDingDingDingDing...Ladies and gentlemen, we have a winner. Of course that name is too long. I'm glad I have y'all to serve as a second set of eyes sometimes.
>>
>>I'll check that Win32s thing, too, despite Tom's warnings....wish me luck.
>
>Good luck Tina on the 8.3 thing. I got bit real hard on a base class when I first started VFP over a year ago. Fortuneatley the customer decided to go totaly Win95. Otherwise I would have had some fun work on my hands.
>
>BTW, it is very nice to be in a position to refuse to do work in Win 3.x (s).
>
>Tom

Wow, you are powerful <g>. Unfortunately, this is a government deal.

BTW, I got the problem solved and installed; now I get a stack error or overload or something as it goes into the load of one particular form. A little old form that just asks where they want the print job to go, and I just suspect that I've hit some sort of wall on that configuration. I'm actually thinking of giving this staff member my test machine and taking his P90 with Win 3.1 as my test machine. The things I do for these people.