Sounds like you have a corrupt database or corrupt Access installation.
First, try compacting and restoring the Access database and see if that works.
If it does not, then open a brand new blank Access database, and then import all your objects from your original database into this new one. Then try doing what was causing the error in the new database.
If you still get errors, I would recommend reinstalling Access on your computer, in case you had a bad or incomplete installation.
I tried to compact and repair the database: same problem
I tried to create a new empty database, and imported all objects of the old one: same problem
In Control Panel/Programs, I selected Access 2013, clicked on Change then on Repair: same problem
I have both Access 2003 and 2013 running on my PC: is it a problem?
Was the database created in Access 2003 or Access 2013?
Can you try it on a computer that only has the one it was created in, and see if it works there?
If it does, then you confirmed your suspicion.
Without seeing the database, there probably isn't much we can do to try to tell what is going on. Note that you can upload your database here. Just be sure that if you do that, you remove any sensitive/personal information.
I do not have the ability to download the database from my current location (corporate download policy), but others do, and I may be able to download it later today or tomorrow.
Some trials:
- I can create a new .mdb (Access2002-2003) database with Access2013, but as soon as I create a new table field with the type "Number", it crashes.
- I created a new .accdb with Access2013, I could create a new field of type number.
- I saved this new database to a .mdb file; when I open this .mdb database with Access2013, I get back to my problem.
- I opened this .accdb database, but again it crashes as soon as I select the Number field.
I suspect the installation...
Database1.accdbDatabase1_to_Access2003.mdb
Check also to make sure that you have the newest release/patch of Access 2013. Sometimes, the earliest versions have some bugs that they address and fix later.
It happens due to Add-ins.
In Access, under File>Options, go to Add-ins tab. At the bottom of the screen there is a drop down labelled "Manage" and along side it, a button labeled "Go ...".
Press it!
After a warning about closing and re-opening the database, a COM Add-Ins widow pops up. If it has an available Add-in "Send to Bluetooth" and the check box is checked this is your problem. Uncheck it. Save changes and cloase out of Access and relaunch.
Reference: http://social.msdn.microsoft.com/For...4-d06e994e9ec3
Unfortunately I stepped back to Access2010 before trying this COM Add-in suggestion...
In Access2010 I do not have this problem anymore.
Thank you to all!