Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2003

    Exclamation Unanswered: ADP, SQL7.0, access violation on oleaut32.dll/msado15.dll

    I created an MS Access Project (.adp) with an SQL7.0 backend.

    I have a very simple Bound form with textboxes and labels (I removed the combo box and subforms, to isolate the access violation, but it didn't help). This is bound to a flat table, not a query or relationship.

    When updating certain records, most especially when checking off one of the checkboxes, you'd see "Calculating..." on the status bar and then the ADP would crash: "Microsoft Access has encountered a problem and needs to close..."

    Only affects certain records.
    Checkboxes are Tristate = No
    Back end table for bit datatypes (for the checkboxes) have default value = -1
    Default value is also set on the form.checkbox

    I already updated to Office xp SP2...

    Any ideas? Any help is much appreciated.

  2. #2
    Join Date
    Mar 2002
    Bielefeld, Germany
    Try removing the default on the form and set the default on the table to 1 instead of -1.

    Does this help?


  3. #3
    Join Date
    Feb 2003
    Thanks, Cris... Let me try this... I'll let you know... Allan T.

  4. #4
    Join Date
    Feb 2003
    Chris, No help... It didn't work... I'm still getting errors on msado15.dll...

  5. #5
    Join Date
    Apr 2004


    Hello there,
    I'm experiencing almost the same problem you previously posted on dbforums, titled, "ADP, SQL7.0, access violation on oleaut32.dll/msado15.dll"

    I'm wondering if you ever found a resolution to the error that you had described. And if so, I'm wondering if you would kindly share...

    My app is also in ADP (Access 2002) format and use SQL 2000 (MSDE edition). My problem occurs when editing data. To reproduce this error:

    1. Open Main Form (record source: a view)

    2. I click one of Combo boxes, used for looking up a record...
    Private Sub Combo20_AfterUpdate()
    ' Find the record that matches the control.
    Dim rs As Object

    Set rs = Me.Recordset.Clone
    rs.Find "[AgencyName] = '" & Me![Combo20] & "'"
    If Not rs.EOF Then Me.Bookmark = rs.Bookmark
    End Sub)

    3. Then in the detail section of the form, I would try to edit data on any one one of the columns (either check boxes or text fields)

    4. Then Access quits with the following error:

    "Microsoft Access has encountered a problem and needs to close. We are sorry for the inconvenience.
    The error report contains an error signature.. "

    The Error signature looks similar to this:
    AppVer: 10.0.2627.1
    ModName: msado15.dll
    ModVer: 2.71.9030.0
    Offset: 0004537d

    I've attempted to Run "Detect and Repair" and have also installed the latest XP Office updates, XP SP-3.. But I'm still getting this error.

    Note: the problem doesn't occur when editing -- as long as I don't use my lookup combo boxes..

    Any knowledge sharing would be greatly appreciated. Thanks in advance for your help!

  6. #6
    Join Date
    Jul 2004

    The same error

    Dear atagayuna and ctsdbowner,

    I have the same error with ADO, when using adp with SQL Server background.
    I don't have solution to the problem and Microsoft (at Hungary) couldn't help me.

    The error in details:
    I've just put my Acc97 application to an Acc2002 project / MSSQL2000 server solution. The convert process was succesful but from then I continually receive the annoying message from Access2002 on certain button clicks:

    "Microsoft Access has encountered a problem and needs to close.
    We are sorry for the inconvenience."

    From Access/Help/About Microsoft Access

    Event Application Failure
    Application msaccess.exe
    Version 10.0.4302.0
    Module msado15.dll
    Module Version 2.71.9030.0
    Offset 0004537d
    Date 2003.06.10. 13:30:44

    Application name Microsoft Access
    Version 10.0
    Build 4302
    Product ID 54185-640-0000025-17197
    Ado version 2.7
    VBA version 6.03
    References VBA, Access, stdole, ADODB, OWC10


    If somebody has the solution, please answer me on

    Laszlo Gombos

  7. #7
    Join Date
    Apr 2004

    Add vb Error handling code

    Hell there,
    I no longer experience the error since I added error handling code to every
    routine (all functions and subprocedures) that I write.

    You may already know this.. but if not, I hope that the following tip will help:

    The following is a basic error handling code that provides a better way out when there is error in your code, rather than allowing the application to quit unexpectedly:
    Function MyCode()
    On Error GoTo Error_Handler
    DoCmd.OpenReport "rptScript", acViewPreview
    'OpenReport "rptScrpt"

    Exit Function

    MsgBox Err.Description
    Resume Exit_Error_Handler
    End Function

    The above code will not help identify exactly which is the
    problematic line of code... You can add a breakpoint at the suspect line,
    then step-through your code, or expand your error handling code.

    I recommend "Access 2003 VBA" book. For adp projects, I strongly recommend "Microsoft Projects with Microsoft SQL Server" book. Both books are good resources.

    I hope that some of this is helpful -- best of luck,

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts