Fatal Application Error

[HighlandJinx]

The software I code is packaged using Visual Studio Installer and tested. One crazy error is occuring that has baffled myself and the rest of our support team. When we use the software via VB6 no errors occur, yet when we run the software with VB6 closed, the software produces a fatal error and closes, when in the middle of a process. Now this does occur in the same place every time, but the last week has been spent error trapping and the error occurs in different places, no warning is given, it just dies...

I think there might be a memory issue, with a lot of variables being stored in various procedures and variables. Can anyone out there tell me of a method of viewing memory used by the program or if i am just chasing shadows?

It is strange as when i install the software on my machine which does have VB6, the software works fine if i run it through VB6 and debugging brings up nothing, yet when i run the software exe, not using VB6, it always crashes after a certain procedure that has just completed stroing data to an mdb via an ADO.

Any help would be appreciated, i'm stumped for the time being.

 

[Sheco]

"... packaged using Visual Studio Installer ..."

Does this mean that you are using the Package & Deployment wizard and have included all of the dependancies?

 

[johnwm]

??MDAC version??

________________________________________________________________
If you want to get the best response to a question, please check out FAQ222-2244 first

'If we're supposed to work in Hex, why have we only got A fingers?'

http://www.essexsteam.co.uk

for steam enthusiasts

 

[HighlandJinx]

all the dependancies have been included, believe me that was a whole other problem a few months ago, I think i've actually fixed the issue now but still baffled as to why it didn't occur running VB. At some point a userID value is overwritten with a NULL value, when the data collected is added to a database, when it comes time to add the userID it falls over because of the NULL value, but it only happens outwith VB... I have now added an error trap to catch the error but still worried that if one value was overwritten like that for, as far as i can see, no reason at all, then it may happen to others that i may have missed,

Thanks for your input guys.

Oh and i run the latest MDACs.

 

[HighlandJinx]

Spoke too soon... I think there is something worse at work here, Noe the error is happening at random, I oculd be using the software for half and hour and it would work ok then, suddenly, it may crash and give no error warning. Then next time it may happen after five minutes, always doing the same stuff... I've error trapped this baby to high heaven and I aint getting anywhere.

I think i've discovered it may not be a coding fault. Is it possible that the application i created and installed may have a limited memory base? The reason i ask is because the software is intensly based on sotring records to a database, but first collecting the data and storing them in variables and once the user has completed their list of objects, it is then stored to an mdb. The crashes always occur when start a NEW batch of objects to be stored.

Just a thought.

Its a tough one...