>>>>>My client and I are developing different applications in Visual Foxpro. We seem to be having common problems with forms, grids, child forms, etc., that end in one of two scenarios: Either the application refuses to acknowledge input (it will accept the task kill message from Windows 95, however), or it will simply hang. On occasion we will receive a GPF from KERNEL32.DLL, but that appears to be more the exception than the rule.
Snip..
>>>Could you elaborate a little more on the scenarios you spoke about? We're not converting from FP 2.x, not using foundation READs, but we are using multiple business objects on a form, and it might be possible (although unlikely), that a textbox is not initialized properly. The other commonality between environments is that we're both using application frameworks...just two different ones.
Snip...
>Cetin,
>That is quite a list. How many of these would not normally generate an error with the same code running in VFP 3.0?
>
>Ed
You mean "same code running on different machines" ? Normally except the ones related with code none of them should occur.
What I do for isolation :
-Check the same app with fresh empty data.
A)On the same computer different dir.
If works ok, corrupted data files ?
B)On a different computer.
If works ok, device driver error, hardware error or simply corrupted VFPxx.esl, dll in system dir ?
-ESL and DLL refreshed still errors
A)Create a basic form with simple new database and tables, few controls, command buttons invoking printer driver.
B)Doesn't still work.
Most likely to have hardware or device driver error, or VFP installation is wrong.
C)Try running VFP self examples.
D)If network then try local (network errors). Both with exclusive and nonexclusive use.
E)Works. Then most likely to have a code error. Trace how the error is reproduced, put suspends (asserts) in code and debug.
Cetin