>>>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.
>>>
>>>I have not scanned UT, so I apologize if this was discussed and resolved previously. If that is the case, I would appreciate being directed to that thread(s). Otherwise, any input would be appreciated.
>>>
>>>Thanks
>>>
>>>Wardo (Ed Johnson)
>>Many scenarios to produce it. ie: Converted screens from FP 2.x, multiple screen, w/o foundation read, one of the textbox's have when = .f.
>>Another one that is not related with FP is printer driver faults (For some HP and Epson printer drivers after a print routine is called somewhere crash could occur -not just after the routine-). Corrupted indexes and so on.
>>Some of the problems are corrected in service packs.
>>Cetin
>
>The crash problem due to the printer driver is due to some problem internal to Windows 95. An interrupt from the mouse messes up the print job if it is still spooling to the printer. I saw some similar reference to it on Microsoft's support site, but couldn't get their solution to work.
>
>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.
>
>Ed
Well Ed,
Some more sceneraios :
-An exe with no "read events".
-Trying to lock a locked record and having no escape.
-On novell many deleted tmp files with no purge at all.
-Transgressed handle (really don't know what it means).
-Corrupted indexes that seem to be working as intact.
-Corrupted indexes and multiple "same value" primary or candidate keys (no warning as violation).
-Also w/o a mouse you could generate printer driver error (GPF) on a local printer (no spooling) with faulty pr. drivers (other programs such as Word could print normally).
-Some third party activeX controls.
-Lost clusters.
-Bad sectors.
-Corrupted dll files.
-Corrupted registry.
-ie:Some pairs cut UTP connections (also faulty other type of network topology).
-"On key label" events called when they shouldn't (interrupt).
-Recreation of an existing object with assigning to the same reference.

There should be many more, these are I can remember for now.
Cetin