Vb 6.0 app in win2000 dont work in 98

[CortexWayne]

I have built a VB 6.0 application sp5 on windows 2000 sp2. Everything works just fine when I run it on win2000. Then on win98 it just shut down and reboot my computer. I think it's a memory problem... But it doesn't display the memory error I had a year ago.

To solve my problem I took a win 98 computer, install VB 6.0 on it and open my code, it does the same thing when I run it with vb. It freeze my computer and reboot. It happen always on one particular form. (wich is the biggest)

I will now try to minimize my form to have the lowest memory needs. I'll will transform every things in array.

Since it doesn't send me any error message, I am limited in my search.

Any help, hint, comments are welcome

Martin Lamontagne
Programmer
CortexWayne@hotmail.com

http://www.FirebladeExperiment.com

 

[Hypetia]

Try to run your program in Step mode using F8 and see what statement or line of code causes your computer to reboot.

 

[CasperTFG]

High Cortex what kinds of things are your trying to do with the program. SO you use COM objects?

Craig, mailto:sander@cogeco.ca

In the computer industry, there are three kinds of lies:
lies, damn lies, and benchmarks.

 

[CortexWayne]

it reboot on a recordset.update most of the time but sometimes it works fine and crash somewhere else... Usually two or three lines later

 

[CortexWayne]

No! It is an inventory and submission system with a simple access database, no com or anything else. My database is linked with ADO connections... as easy as this...

 

[awelch]

You may need to install DCOM98 on the machine since your app was developed on a 2000 machine. Here are some articles that may help.

Microsoft article on how determine the DCOM you have installed:

http://support.microsoft.com/default.aspx?scid=kb;en-us;232003

DCOM98 release notes:

http://support.microsoft.com/default.aspx?scid=kb;en-us;196208

Hope this helps. Good luck!

Andrea

 

[CasperTFG]

You will most probably need a new MDAC... but your best to try and find the line where it last ends. The memory problems are real buggers since you can't stop and see the last line executed so you just have to hope you remember what it was before the crash.

Craig, mailto:sander@cogeco.ca

In the computer industry, there are three kinds of lies:
lies, damn lies, and benchmarks.

 

[CortexWayne]

thx a lot Awelch I'll look foward and I'll return with that.

 

[CortexWayne]

I have install MDAC 2.7 on the running machine, nothing changed... MDAC seems not to be the answer

 

[tsh73]

CortexWayne,

Is anything linked to your recordset?
May be smth wrong with bound control?

I remember once I have a problem - RTFBox suddently assumed huge size on another machine... So it just crashed

 

[JohnEfford]

Hi

There are a number of different versions of MDAC do the, you have installed a new version on your target PC, do the versions on the target PC and development PC match?

It might help if you posted the area of code were the memory error is occuring.


Regards

 

[tedsmith]

I had this problem with one form, Turned out to be a corrupted text box. I had copied and pasted controls instead of making new ones. Sometimes it would only crash the exe and not in the VB6 development editor mode.
It would freeze everything.
The way I found out which one was to make a dummy copy of the whole sourcecode folder to experiment with then
I removed each control one by one until it didnt happen.
I first removed half the controls then the other half then half of the half and so on and found it pretty quickly (like a binary search!)
ALSO you might have a routine that is chasing up it's own fundamental orifice. Check you havent used the same variable name in different routines or one sub is not calling itself.
EG. if you had a for next loop with a sub in it with the same public variable then the for next loop will never end.