Hi all,

Our FoxPro2.6a aplication run's in windows with very few glitch's(theirs always some) recently we have run into a problem that im unable to explain or find help on.

Let me explain the simple basics of the problem we are having,

Our customers goes thru an update process, after we transfer all data from a transaction file to the Master files, we go thru and print them a few reports, based on the info we are about to purge from the tran file. This is a fairly routine process that is run numerous times thru out the day. Some customers have the option to filter the data in the transaction file and only update 300 of the 5000 records lets say.

So after mass release of Version 3.3.1 we began our next versions, 3.3.2, 3.3.3, 3.3.4 then had to do some more major feature changes and have now switched to 3.4.1, and 3.4.2,

With one of our recent builds of the program V3.3.1, we have run into a problem that when the foxpro print dialog comes up the program is freezing up, now we distribute to multiple customers with many diffrent computer layout, so the only info i can give you is how it is setup within my office.

so now into the more nitty gritty of the problem

About a month ago customer(A) called in with the problem of not being able to update without freezing on the print (first report), we got the customers data and recreated the problem here, after many hours of tweaking everything we could think of, we had one of our programmers accidentally try it on V3.3.2, and Presto, it updated with no problems, so we look back at the code changes between 3.3.1 and 3.3.2 and nothing in this routine, or with these reports has changed, so we say its just another of those unexplained problems with windows not liking the DOS environment.

So a week later customer(B) calls in and has the same problem, but with a different update routine , so after an hour of testing different scenario's we try v3.3.2 and presto, again this takes care of the problem, so now 2 weeks later customer(H)(had a few between now and then but not every customer) who is running 3.4.1(needed one of the major changes) calls in and is have an even stranger problem, he is updating his customers using our filtering method, so he has lets say 3000 files he has to update, filter 1 is customer 1-500, filter 2 is 500-1250, filter 3 is 1250-1600, filter 4 is 1600-2400, filter 5 is 2400-3000. so their problem doesnt fit within the previous scopes cause of 2 reasons, 1 he isnt in version 3.3.1, and he was able to update all of the files in 4 diffrent updates but for filter 3, no matter how he tries to update filter 3 it will not go thru. so i being the long process of checking all the possible solutions, i changed config.fpw(no other config files are used in the program) and many other things, now if i bring the customer data to my machine, i have no problem updating the filter 3 but only when i do it with a fox pro enviorment loaded before the exe is launched, otherwise i freeze at the exact same placement. So after a couple days of testing and playing around with the data, i break down and say, ok im going to try version 3.3.2 and see if it works, PRESTO, it works.

So i know have a semi solution, i go thru everything and can only find 1 diffrence between our build of 3.3.2 and 3.4.1 and that would be, the prior to the final build of the executable for distrobution, on 3.3.2 we got everything from Source Safe, in version 3.4.1 we did selective downloading(inital download was everything from Source Safe, but after chages required during testing of the version, we had things for 3.4.2 already in their). so that the only main changes i can see between the 2 builds(of course some code changes but nothing in any of these sections.

So i come to today, today i made version 3.4.4 with this version i made sure i got all of SS out, and after creating the exe i tested with customer(h) data. and i am still freezing.

Now let me go thru all of the basics that we do for testing of problems like this(usual one of these things solves any freeze while printing issue)

- replaced foxw2600.esl
- changed config.fpw, multiple changes including maxing out values, and taking them down to the bare min.
- (full delete of the sub directory) uninstalled and reinstalled version update with their data set
- downloaded new .frx's and compiled the program again.
- used their Full Directory backup, and went thru removing cluttered files in the sub directory
- tried on diffrent machines(3 diffrent programs, 2 helpdesk, 3 test machines, & 2 work stations on customer site)

I am still current having this problem and have run out of other things to look at or try, so any input even to the extreme would be very helpful (and no going to vfp9 isnt possible at this time, that another department that is working on taking it to that version, and till they are done, im stuck with this one)

Thanks