Access crashes when query results are copied.

[Chris Hankey]

I having a strange and annoying problem where Access crashes when the
user copies (to the clipboard) the results of a query. The message is
not very helpful. It simply says - "Microsoft Access has encountered
a problem and needs to close. We are sorry for the inconvienience".

The MDB is the front-end portion of an Access application. Most of
the tables are linked to the back end. Including the tables used to
generate the query in question. There are a couple of local tables
that have user preferences. Most of the queries that the users run
use the query by form technique. Overall the application is pretty
simple.

Some of the users have been using the same copy of the front-end. My
theory is that this is causing the front-end to become corrupt. I am
hoping that this problem will go away if all users use there own copy
of the front-end. Has anyone seen this problem? Any help or
suggestions would be appreciated. One quirk is that the error does
not occur consistently on everyone's PC, even if they are using the
same copy of the front-end.

[Darryl Kerkeslager]

In almost every case where I have encountered this error in A2002, it is
because a variable or function has been created that is the same as the name
of:

1. an Access reserved word
2. another variable or function
Darryl Kerkeslager
"Chris Hankey" <ch*****@aegonusa.com> wrote in message
news:38**************************@posting.google.c om...

I having a strange and annoying problem where Access crashes when the
user copies (to the clipboard) the results of a query. The message is
not very helpful. It simply says - "Microsoft Access has encountered
a problem and needs to close. We are sorry for the inconvienience".

The MDB is the front-end portion of an Access application. Most of
the tables are linked to the back end. Including the tables used to
generate the query in question. There are a couple of local tables
that have user preferences. Most of the queries that the users run
use the query by form technique. Overall the application is pretty
simple.

Some of the users have been using the same copy of the front-end. My
theory is that this is causing the front-end to become corrupt. I am
hoping that this problem will go away if all users use there own copy
of the front-end. Has anyone seen this problem? Any help or
suggestions would be appreciated. One quirk is that the error does
not occur consistently on everyone's PC, even if they are using the
same copy of the front-end.

[Keith Wilby]

ch*****@aegonusa.com (Chris Hankey) wrote:

Some of the users have been using the same copy of the front-end.

A definate no-no. Also, have you implemented the changes detailed here?

<http://members.iinet.net.au/~allenbrowne/ser-48.html#usability>

Regards,
Keith.