>Hi everyone,
>
>This has never happened to me before... I'm doing some work in an old Foxpro for DOS system and the production version is crashing (no errors, just closing) whenever this one process is run. It involves queries of fairly large sets of data (only two tables though). The temp directories are set to the local PC drive. The only time it crashes is if the program is run from the production server, using production data and outside the Foxpro environment (ie, running from a desktop shortcut). Every other possible scenerio results in the program running correctly and returning expected results. I've run all the obvious variations you would normally try, production versus development data/application, but nothing else causes the error. I've refreshed all the application files in production as well as refreshed the data in development. The biggest problem is that the production server is in another state (geographic) and since the problem only occurs outside the Foxpro environment, I can't
>track and debug exactly what's going on when it drops-out. The production server has been rebooted to clear up any possible cache issues. The config.fp file exists in the directory where the main exe resides. We don't want to have to copy the entire production environment down to development as it's about 3gig and would tie up too many resources, both in time and personnel. Is that our only option? Does anyone have any ideas? I'll check out even the most obscure possibilities at this point...
>
>Regards, Renoir

There are several hardware things I would try... (1) another PC, (2) replace the memory, (3) replace the video card, (4) replace the NIC.


HTH