ADO Connection Object

When I am closing an ado connection object using the command (conts.close) I get the following error message:

"Unhandled exception in VB6.EXE (MSADO15.DLL):0xC0000005: Access Violation"

The error occurs on some machines, while it does not occur on others.

Please help me out.

Thank You.
LVL 2
alokanantAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
rpaiConnect With a Mentor Commented:
Check the Service Pack installed on those machines that comes up with that error message. The access violation errors used to occur when unregistering an ATL DLL or EXE built with a version of Visual C++ prior to 6.0 on a computer with the Visual C++ 6.0 Atl.dll installed. This  was, however, fixed with Service Pack 3. So Service Pack lower than 3 could be a potential cause of the problem.
0
 
ketapillarCommented:
Try this where conn1 is you connection object

If conn1.state <> adStateClosed Then conn1.close
Set conn1 = Nothing


0
 
alokanantAuthor Commented:
I have checked the status of the connection object, it is adStateOpen before I attempt to close the database.
0
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

 
alokanantAuthor Commented:
I have built the application using Visual Studio 6, Service Pack 5.

The PC on which the problem occurs does not have Visual Studio. All the machines on which I am testing the application run on Windows 2000 Service Pack 2.
0
 
alokanantAuthor Commented:
I have built the application using Visual Studio 6, Service Pack 5.

The PC on which the problem occurs does not have Visual Studio. All the machines on which I am testing the application run on Windows 2000 Service Pack 2.
0
 
mubashar_iqbal_csCommented:
Perhaps u are not cheching the status of ur connection before closing the connection. Try it before closing the connection.
If conts.state <> 1 Then
   conts.close
   set conts = nothing
0
 
rpaiCommented:
Yet another cause could be an incorrect reference. Or
probably an incorrect tear-down of an ActiveX control in your application.

Also, take a look at this article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q248837

Hope this helps.
0
 
alokanantAuthor Commented:
mubashar_iqbal_cs:
I have already checked the status of the connection object.

rpai:
what do you mean by "incorrect tear-down of an ActiveX control". How can I check whether this is happening in my application
0
 
rpaiCommented:
Incorrect reference could be the potential cause.
Maybe the version of ADO.

To check if its your application might be causing this error, you need to code for appropriate error handlers.

On Error Goto ErrHandler
.
.
. 'Your code
.
Exit Function
ErrHandler:
 App.LogNTEvent Err.Description
0
 
PNJCommented:
Check MSADO15.DLL, there are several weird versions. The one dated 27/11/2000 works OK (with Vb5 anyway)
0
 
DanRollinsCommented:
Hi alokanant,
It appears that you have forgotten this question. I will ask Community Support to close it unless you finalize it within 7 days. I will ask a Community Support Moderator to:

    Accept rpai's comment(s) as an answer.
    *** Also, nobody said: Update MDAC on failing computer.

alokanant, if you think your question was not answered at all or if you need help, just post a new comment here; Community Support will help you.  DO NOT accept this comment as an answer.

EXPERTS: If you disagree with that recommendation, please post an explanatory comment.
==========
DanRollins -- EE database cleanup volunteer
0
 
SpideyModCommented:
per recommendation

SpideyMod
Community Support Moderator @Experts Exchange
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.