Crosstab query problem

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.
 
M

MGFoster

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Be sure the AutoCorrect option is turned off before you change any
object/field names. After you've copied/renamed the table compact the
db; this will get rid of any "ghost" copies of the original table.

When converting from one version of Access to another it is best that
the original db doesn't have any compiliation errors. So before
conversion compile & compact the original version. This will discover
any errors. Correct any errors before conversion.

--
MGFoster:::mgf00 <at> earthlink <decimal-point> net
Oakland, CA (USA)

-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBQJLjl4echKqOuFEgEQKsrACgx2xI/PRL7PlQxrcMxCn+acbFS7QAn3B3
R70VFEPhm+1NKFD8bT5CihK/
=/Vlf
-----END PGP SIGNATURE-----
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top