|
-
Nov 19th, 2002, 05:32 AM
#1
Thread Starter
Lively Member
DBGrid Error
Hi, I am having a problem with my data grid. It’s not a simple error, but it is shutting down the application, and VB if I was debugging, I try t debug, but nothing wrong in the code. And it’s not a standard one, which means it doesn’t appear always. I am calling a form with a datagrid in it from inside another datagrid. I am getting the following message:
This Program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.
VB6 caused an invalid page fault in module DBGRID32.OCX at 017f: 230fc8b0.
Registers:
EAX=00000000 CS=017f EIP=230fc8b0 EFLGS=00010216
EBX=00000100 SS=0187 ESP=007fef60 EBP=00000808
ECX=007fefa8 DS=0187 ESI=03accdc0 FS=32ff
EDX=03ace020 ES=0187 EDI=03accce8 GS=0000
Bytes at CS: EIP:
8b 97 e4 00 00 00 8d 7c 24 08 c1 ea 01 8b 0f 80
Stack dump:
03acd254 03accce8 00000000 00000000 00000000 00000000 23111ef9 00000100 007fefdc 007fefac 007fefa8 007fefec 007fefd4 00008044 007ff020 c1500001
Some times when I say close, it gives me the message above once more, and re close, other times it gives me the following message, and don’t close at all till I cut the power of the PC.
This Program has performed an illegal operation and will be shut down.
If the problem persists, contact the program vendor.
VB6 caused an invalid page fault in module KERNEL32.DLL at 017f:bff9dc5d.
Registers:
EAX=c00301a8 CS=017f EIP=bff9dc5d EFLGS=00010212
EBX=007ffe28 SS=0187 ESP=006fff7c EBP=00700218
ECX=00000000 DS=0187 ESI=00000000 FS=32ff
EDX=bff76855 ES=0187 EDI=bff79198 GS=0000
Bytes at CS: EIP:
53 8b 15 54 ad fc bf 56 89 4d e4 57 89 4d dc 89
Stack dump:
So what Do you think, is it a DBGrid32 problem, or a problem with coding in someway? Please help me it’s very urgent.
-
Nov 19th, 2002, 03:30 PM
#2
Does it happen only when run in the IDE?
Only when compiled?
Have you tried running it on different machines?
Are you sure your DBGrid component is healthy (not corrupt)?
-
Nov 19th, 2002, 04:16 PM
#3
Fanatic Member
I would hate to see what happens when you cause a "complicated" error. 
Can you define what you mean when you say you are calling a form from within a datagrid? What even triggers this? Modal?
Can you isolate the problem? if you put a button on a form and try and call that same "problem" form, does it bomb?
How are you hooking up the data in the first and second grids?
data controls? manually? combination of both?
Are they reading/locking/editing the same records?
-
Nov 20th, 2002, 02:05 AM
#4
Thread Starter
Lively Member
Some more Details
Thanks Hack and JPicasso for your replies.
The error is showing many times, not always, in all cases, complied or in IDE, and I tried at 4 different machines, with different RAMs and Processors, the same problem. What is getting me lost is tha it doesn't appear systematicall which ean I am not beeing able to know exactly when it does appear, for tenth it does and once none without having changed any think.
I think that my DBGrid is healthy for I used it in many other places but didn't have any problems.
The DBGrid giving the error is named Grid B, It's a help grid linked to DataB recordset in the form formB.
I am calling this formB from either the GridA in formA or from a buttonclick on formC. In both cases I am getting the problem.
Data in both grids are independent. T am getting the value I want from GridB ina avariable, and pasting it in Grid A.
Hope I was clearer, and waiting for a reply from your parts.
-
Nov 20th, 2002, 09:47 AM
#5
Fanatic Member
Hmmm.
Sounds like a toughy.
There is nothing immediatly obvious to me.
Interrmittent errors are the worst.
Try adding debugging comments into your code either
wtih msgboxes or a log file..
here is a quick log file that I use for debugging purposes...
VB Code:
Public Sub Loggit(pmess As String)
Dim filenum As Integer
filenum = FreeFile
Open App.Path & "\Logger.txt" For Append As #filenum
Write #filenum, pmess
Close filenum
End Sub
Put that in a module and call the function several times in your code.
especially just before and just after you call the formB and when you are setting the source for the GridB and such.
Some second thoughts... are you closing the form properly when you are done iwth it?
Do you open the form modally?
Is it possible that opening the form and then calling it open again when it has not been closed is a problem?
-
Nov 25th, 2002, 04:56 AM
#6
Thread Starter
Lively Member
will try it
Thaks JPicasso, I will try this.
In fact I am working with DAO connection, do you think that Changing to ADO connection will solve the problem?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|