Hum I really need help on this one

[Boumxyz2]

My VB application is running very stable and very well on win98, but on NT it is running stable on one of my test computer and on the other one I'm getting a run time error after form terminate once in a while. Could it be OCX file or DLL causing the trouble ?

Anyone can help me ?

Thanks
Nic

[DSJ]

What is the error number and message?

[DeafBug]

A little extra information will be helpful. What are you running? Are you creating objects? Did you forget to set them to nothing?

Win98 will tolerate a little, WinNT will not. Gives a reason why NT or W2K is stable OS than 98.

[Boumxyz2]

Using files that I all close and using Api calls
(Open process, WaitForSingleObject, CloseHandle)..
Using Inet control and standards control (buttons, textbox and the likes )...

I'm really lost here.. It work on 1 NT workstation and it doesn't on the other one..

I can't figure it out..

Thx for your help
Nic

[Boumxyz2]

Here's the error message

The instruction at 0x70223EFF referenced memory at 0x70223EFF. The memory could not be read. It's a system error message. Does the same when I run it with the VB debugger.

It's not an ordinary VB Runtime error. Usually you get a code and it highlight your instruction in yellow and the like.. But now it's the system that finds the error and then it happens after form terminate because I actually put MsgBox in Form_Unload event, and Form_Terminate event.

I'm really lost...

Thx for your help.
Nic

[DSJ]

About the only thing I can suggest is to make sure you have corresponding CloseHandle calls for all your OpenProcess calls. I think it probably is an API call issue.

[Boumxyz2]

All process Handle are already closed and still I'm getting that error message on 1 station and not on the other one.

I'm lost.

Nic