Invalid Arguement

[tkoping]

Working with Access 2003 SP3. Have a table that we past in from Excel a list
of all employees. We then run a make table query to create a unique Id by
combining a couple of the fields. This table and query have worked this way
for several years with no issue (where origianally designed in Access 2000).
Suddenly, when running the make table query, we got an "Invalid Arguement"
error. While trying to fix it, we tried to cut down on the data, and started
getting an exceeded sharing error. That was resolved by restoring the data
from a back up, but now even when I try to create a new table in the
database, it will give me the Invalid Arguement" error, even if I create a
one column table with a generic heading using the table wizard. Is my
database corrupted? If so, how much can I use to create a new database or do
I start from scratch (days of work)?

 

[Jeff Boyce]

If there is some form of subtle corruption in the database, there are a few
options you can try before rebuilding from scratch.

First, though, make a backup copy. Now make another one. Maybe even a
third <g>!

Have you tried opening a code module and running the Debug/Compile command?

After compiling your database, you can exit the code modules and see if
Compact & Repair helps.

You might consider looking into (an on-line search will find the
particulars) running Access in "decompile" mode.

You might look into creating a new (empty) Access database and importing all
the pieces from your questionable db.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[tkoping]

Thank you. I was in the process of importing into a new one when I got your
post. Somehow, doing so reduced the size of the DB from over 2 gbs, to
..3gbs. All the data is still there. I don't know where the extra size came
from, but it is running better. Thanks.

 

[Jeff Boyce]

Several factors contribute to "bloat".

If your database is using "temporary" tables (creating/deleting "make
tables"), that adds to bloat.

If your database stores images, that bloats the db.

Good luck!

Regards

Jeff Boyce
Microsoft Office/Access MVP