Illegal Operation - Invalid Page fault(Resolved)

Hello

I just got through making a bunch of changes to my app and now it when I click on certain buttons I get a message box saying:

This program has peformed an illegal operation and will be shut down.

The details window has the following info:

Sorter caused an invalid page fault in
module KERNEL32.DLL at 019f:bff7d383.
Registers:
EAX=003002a3 CS=019f EIP=bff7d383 EFLGS=00010202
EBX=82262262 SS=01a7 ESP=0080dee0 EBP=0080df00
ECX=82261404 DS=01a7 ESI=09160c18 FS=1817
EDX=00600000 ES=01a7 EDI=00605000 GS=0000
Bytes at CS:EIP:
66 8b 17 83 45 0c 02 0f b6 fe 0f b7 3c 7b 8a da
Stack dump:
82261404 000004e4 005e37f0 00000000 006e00cc 00600550 002ef69b 09150000 0080df34 bff7d0b0 82261404 00605000 00be3d36 09150010 00600545 00000000

I don't want to take out all the work I just did and start all over as it was 3 full days worth of coding.

It does the same thing if I launch the app in the IDE or from a compiled exe.

Any Ideas on what went wrong.

Regards

David

Can you show the code that causes the problem?

Do these buttons share common code (or a common sub/function)?

Code:

---

Private Sub cmdOK_Click()

'{snip}
frmFiltersTabs.txtBidGroup.Text = DBBidGroup
frmFiltersTabs.txtBidNumber.Text = CurrentBidNumber
'{snip}

Unload Me
Set frmOptions = Nothing

End Sub

---

....and where does it fail?

Well, your procedure went too huge.
Split it into a few smaller procedures.
And after each procedure finishes, call msgbox to inform u
that the procedure has just finished executed.

And the last msgbox just rite b4 it abends will tell you which
part of the code fails.
and from there you may ask more specific questions regarding
that part or debug it yourself cuz' ur procedure is too long.:eek:

Well it seems that the problem is in the sending of strings to a text box on a form that is not loaded yet(The 2 textbox lines in the middle). I'm not sure why this happens. And it doesn't happen if you step thru the whole process. Only if you let it run. Go figure.
What I did is to do a loop thru the forms collection to see if the form was loaded and if it wasn't then I didn't send the string. Then I put the string into the form load for the target form to get the info there when the form finally is loaded.
Marty's question unlocked my brain and got me of my lazy duff.
Well that's my story and I'm sticking to it.

Thanks

David