By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
459,920 Members | 1,660 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 459,920 IT Pros & Developers. It's quick & easy.

Microsoft Access has encountered a problem...

P: n/a
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???

Feb 5 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
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.
"bo**@4bcx.com" <bc******@ix.netcom.com> wrote in message
news:11**********************@g14g2000cwa.googlegr oups.com...
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???

Feb 6 '06 #2

P: n/a
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

Feb 7 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.