Microsoft Access has encountered a problem...

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • bobc@4bcx.com
    #1

    Microsoft Access has encountered a problem...

    Any help appreciated with this problem --

    I have a Microsoft Access 2002 application. The Access
    mdb has a refence to DAO 3.6 (not ADO). A form is bound to
    a linked table in a second mdb. In the AfterUpdate event
    method of a text box, after a SaveRecord, a method is called which is
    in a
    GlobalMultiuse class in an ActiveX code component that I
    compiled in VB6. In this method, a DAO recordset is
    opened on the same record in the same database table that
    the form is linked to, and then, some
    fields of the record are modified with rs.Edit / rs.Update, and
    then the recordset is set = Nothing. These
    modified fields are also shown on the Access form.

    I have tried this technique on a small test app, and all
    works fine: the changes appear on the Access form.

    However, in my app, the AfterUpdate results in:
    "Microsoft Access has encountered a problem and needs to
    close. We are sorry for the inconvenience."

    Clicking a button brings up s screen that says ModName =
    dao3600.dll.

    I have seen this message in other Access apps, but
    usually I can compact & repair or import all objects into
    a new MDB and that fixes it. Here though it happens every
    time.

    Any ideas how to proceed???

    Tags: None
    • Rob Oldfield
      #2
      Re: Microsoft Access has encountered a problem...

      Access and the Jet engine are both fully up to date with service packs? If
      you're using the db on multiple machines then ensure that that's true for
      all of them.


      "bobc@4bcx. com" <bclemens@ix.ne tcom.com> wrote in message
      news:1139173943 .058850.262670@ g14g2000cwa.goo glegroups.com.. .[color=blue]
      > Any help appreciated with this problem --
      >
      > I have a Microsoft Access 2002 application. The Access
      > mdb has a refence to DAO 3.6 (not ADO). A form is bound to
      > a linked table in a second mdb. In the AfterUpdate event
      > method of a text box, after a SaveRecord, a method is called which is
      > in a
      > GlobalMultiuse class in an ActiveX code component that I
      > compiled in VB6. In this method, a DAO recordset is
      > opened on the same record in the same database table that
      > the form is linked to, and then, some
      > fields of the record are modified with rs.Edit / rs.Update, and
      > then the recordset is set = Nothing. These
      > modified fields are also shown on the Access form.
      >
      > I have tried this technique on a small test app, and all
      > works fine: the changes appear on the Access form.
      >
      > However, in my app, the AfterUpdate results in:
      > "Microsoft Access has encountered a problem and needs to
      > close. We are sorry for the inconvenience."
      >
      > Clicking a button brings up s screen that says ModName =
      > dao3600.dll.
      >
      > I have seen this message in other Access apps, but
      > usually I can compact & repair or import all objects into
      > a new MDB and that fixes it. Here though it happens every
      > time.
      >
      > Any ideas how to proceed???
      >[/color]


        Comment

        • aaron.kempf@gmail.com
          #3
          Re: Microsoft Access has encountered a problem...

          MDB is crap

          DAO is crap

          Sqeak SQL or pass it to someone who does

          MDB isn't reliable enough for a single user and a single record

            Comment

            Previous template Next
            Working...