Re: Crosstab query problem

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: MGFoster (me_at_privacy.com)
Date: 04/30/04 

Date: Fri, 30 Apr 2004 23:38:56 GMT

-----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-----
Tim wrote:
> 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.

Relevant Pages

  • Re: 2002 database corrupt and unuseable after upgrading to Access 2003
    ... it sounds like you have a partially corrupted A2002 database. ... Compact: Tools | Database Utilities | Compact. ... Try the conversion to A2003 again. ... > corrupt." ...
    (microsoft.public.access.conversion)
  • RE: Compacting MDB help
    ... The autoexec macro opens a ... The FrontEnd.mdb's main switchboard has a cbo to switch back end ... FECompact.mdb runs the few lines of code to compact the FrontEnd.mdb ... I'm quite certain that you can't Compact an open database from within itself ...
    (microsoft.public.access.modulesdaovba)
  • RE: Compacting MDB help
    ... This will cause the database to grow so Compacting ... not split off the tables from your FrontEnd. ... The FrontEnd.mdb's main switchboard has a cbo to switch back end ... FECompact.mdb runs the few lines of code to compact the FrontEnd.mdb ...
    (microsoft.public.access.modulesdaovba)
  • RE: Compacting MDB help
    ... not practical to have staffpersons open another database in order to switch ... When the front end opens, it goes directly to the main switchboard. ... the only reason why you would need to Compact the ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access crashes when opening form
    ... Allen Browne - Microsoft MVP. ... You were correct in suspecting SP3. ... I've also had a problem with "compact on close" not working (it ... database works correctly there. ...
    (microsoft.public.access.forms)