GPF in Datatbl.dll (None Specified)
At 30 MAY 1999 09:43:45PM Bil Vernon wrote:
We have a client who keeps getting a GPF in DataTbl.dll on one particular machine in one particular window. This window has 3 data bound edittables and appears to work fine on every other machine (including our own).
I found a thread on the general discussion forum that describes a similar problem (breaking at the same address), yet we are not using ARRAY (we generally use DEFPROP instead) and this is happening when the window is first opened with a new record.
I have also got them to check for the existence of another version of datatbl.dll and they have found none.
The details fo the GPF are:
OINSIGHT caused a general protection fault
in module DATATBL.DLL at 0026:00000c3c.
Registers:
EAX=00000000 CS=48f7 EIP=00000c3c EFLGS=00000217
EBX=0002ffff SS=3c07 ESP=000051fa EBP=00005200
ECX=000001b1 DS=4e87 ESI=00020400 FS=0000
EDX=0002ffff ES=4e7f EDI=00000400 GS=0000
Bytes at CS:EIP:
f3 a5 13 c9 f3 a4 91 e3 18 0b f6 75 07 8c d8 05
At 31 MAY 1999 10:31AM Oystein Reigem wrote:
Bil,
…yet we are not using ARRAY (we generally use DEFPROP instead)…
But the DEFPROP of an edit table is ARRAY (almost), so it doesn't rule out the possibility of the problems being related. To quote from the writings of St Cameron: "DEFPROP (…) updates bound information, sets the internal data structure which signifies savewarn, then defers to ARRAY".
- Oystein -
At 15 JUN 1999 07:56PM Bil Vernon wrote:
OK, now the GPF is no longer happening on this one particular machine, but is occurring (at apparently random intervals) on other machines. The details are the same and it seems to occur on the create of one window and the deleterow event of another table in a different window.
Any ideas on this, those who are experiencing it find it very distressing.
On a related note, one of our development machines is also getting a GPF in DataTbl.dll (at 0026:0c15) when going to the development menu-]check-out, selecting Check-out/Retry Check-out… and then Edit/Retry Check-out.
This only happens on one particular machine running NT 4.0 (Service Pack 5), pretty much all the time (more often than not). All other machines (Win95) have no problems.