T
Tim
The fault is in Access 2002 SP2 and happens when running
a Crosstab query following copying a table that is
resident in the database and renaming it back to the
original name. It also manifests itself if some rows of
data are deleted from the resident table and the crosstab
query is then attempted to be viewed or run. The
message 'Microsoft Access has encountered a problem and
needs to close. We are sorry for the inconvenience'
appears. By attempting to run the query in an old version
of the database from a backup, I have discovered that by
making the whole database read only the crosstab query
can be viewed successfully and run successfully.
The database was originally used in Access 2000 and has
only been a problem since my machine was upgraded from
Windows 2000 to XP, and I upgraded from Access 2000 to
2002.
a Crosstab query following copying a table that is
resident in the database and renaming it back to the
original name. It also manifests itself if some rows of
data are deleted from the resident table and the crosstab
query is then attempted to be viewed or run. The
message 'Microsoft Access has encountered a problem and
needs to close. We are sorry for the inconvenience'
appears. By attempting to run the query in an old version
of the database from a backup, I have discovered that by
making the whole database read only the crosstab query
can be viewed successfully and run successfully.
The database was originally used in Access 2000 and has
only been a problem since my machine was upgraded from
Windows 2000 to XP, and I upgraded from Access 2000 to
2002.