Are you getting a DLL reference and offset? Dr Watson logs?
We have seen the SAPDB ODBC driver cause application crash (protection fault, etc). Some of our applications never crash, others crash on regular basis. Using a different DBMS / driver always fixes it. It appears to be more multithreaded / concurrent issue - or socket related problems with frequent connect/disconnect to SAPDB server. How does your problem application work - does it have one connection it uses over and over or frequent open/close of database? connection pooling enabled?
Stephen Gutknecht currently in Long Beach, California, USA
-----Original Message-----
From: Benjamin Lukner [mailto:[EMAIL PROTECTED] Sent: Thursday, August 14, 2003 1:46 AM
To: [EMAIL PROTECTED]
Subject: VB6 crashes occasionally
Hi!
We use the following components for our project:
- VisualBasic 6.0 SP5 Enterprise - MDAC 2.7 (ADO) - COMDLG32.OCX - TABCTL32.OCX - COMCTL32.OCX - ComponentOne Studio 2002 - TrueDBText 6.0 - TrueDBGrid Pro 7.0 (OLEDB) - TrueDBList Pro 7.0 (OLEDB) - VSPrinter 7.0 - VSReport 7.0 - SAP DB 7.4.3.X (X = 10 to 27) - SAP DB ODBC Driver 7.4.3.X (X = 10 to 27)
The problem is that sometimes VisualBasic crashes with a Watson (read error) or simply closes without a message. Nearly never when running the program or the exe file but almost always when typing code.
We can open VB with the project, do nothing, don't touch the PC... and after a while VB crashes.
We can't clearly say it's a problem with MDAC 2.7 or TrueGrid and SAP DB but we guess so because we use all these components but SAP DB also in other projects without any problems. So I'd like to know if someone else's got this problem and/or knows what causes it because it's a really nasty behaviour ;-)
Kind regards,
Benjamin Lukner trinomix GmbH
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
OK, here we go:
I started the storage management system and the service program in two VB6 sessions.
Both have ONE persistent connection via ADO to the SAP DB.
In the first program I defined about 10,000 storage locations and deleted them afterwards.
Simultaneously I imported about 8000 articles with the second program and deleted them afterwards.
Then I closed both programs. Short time later both development environments crashed while I opened the windows explorer.
Mostly VB6 crashes while switching to another window!
(Of course normally only one program is running on a machine,
but after 3 whole days sitting in front of VB and waiting for a crash - of course it didn't - I had to provoke one ;-) )
When closing the application, I execute: ADOConnection.Close 'Private ADOConnection As Connection
VB6 version is VB6 SP5 build 6.0.89.88
In the last 2 days it crashed one time with:
[WST_Service - Microsoft Visual Basic (design): vb6.exe - Fehler in Anwendung]
Unhandled exception at 0x04319da0 in VB6.EXE: 0xC0000005: Access violation reading location 0x041d9da0.
another time with:
[WST_Service - Microsoft Visual Basic (design): vb6.exe - Fehler in Anwendung]
Unhandled exception at 0x041d9da0 in VB6.EXE: 0xC0000005: Access violation reading location 0x041d9da0.
AND THREE TIMES WITH:
[vb6.exe - Fehler in Anwendung]
Unhandled exception at 0x03cb9da0 in VB6.EXE: 0xC0000005: Access violation reading location 0x03cb9da0.
("Die Anweisung in '0x03cb9da0' verweist auf den Speicher in '0x03cb9da0'. Der Vorgang 'read' konnte nicht auf dem Speicher durchgef�hrt werden.")
This seems to be the error that occurs in most cases, as far as I remember.
Your turn ;-)
Kind regards,
Benjamin Lukner trinomix GmbH
_______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
