Every time I try to go in and edit code in Access...I get this generic error. In was happening in 2007 so I installed 2003. Still happening. The only thing I have recently installed is SQL Server 2005 Express.

I had this issue a few years ago. I think your database is corrupt.

You're best to open a new database and go to File, Get External Data.
You can then copy all tables, Queries, Forms etc across from the corrupt db.

I had this issue a few years ago. I think your database is corrupt.

You're best to open a new database and go to File, Get External Data.
You can then copy all tables, Queries, Forms etc across from the corrupt db.
No, it happens on ALL databases. New or not.

No one can shed some light on this show stopper? I have uninstalled nearly everything I can and still no dice.

Make sure you have the lastest service packs installed.

Try creating a new empty database and importing everything into it. That will sometimes resolve corruption issues.

Make sure you have the lastest service packs installed.

Try creating a new empty database and importing everything into it. That will sometimes resolve corruption issues.
Like I said, regardless of whether I create a new database or not, it still happens.

its not an installation

its a corrupt =database

sometimes there fixable other times not

go back to a back up, and restore whatever changes you made. You MAY be able ot import objects from the corrupt dbs.

if you havent a backup, try opening a new dbs, and see if you can import objects.

if you can, do a few objects at a time, making sure the corruption doesnt appear again, and make additional copies as you go. It may just be one corrupt form doing this.

AIt would appear that you feel that it is the installation environment, while others feel the database is corrupt. An easy way to sort out the difference would be to move the database file to a neutral site (perhaps a Laptop running Access) and see if it works there (or if any of the suggestions to repair it work there). If you are able to fix it, you know it is most likely not the installation environment.

Good luck!

NOTE: I did not notice if you were Access only or something like Access/SQL Server oriented. If it is the latter, you may need to create a dummy back end to test to see if it works.