make-table error 3001

[Paul]

Recently the Access OfficeXP PC fails on either local or remote
databases when I run a make-table query, resulting in an Invalid
Argument box which upon clicking says it is a 3001 error. The Select
Query mode works fine however.

An uninstall/resintall of Office XP failed to fix this issue. The issue
is with this particular PC. Another can run a make-table query on the
remote database without problems.

Any ideas? Thanks.

 

[JohnFol]

So, using the other PC scenario this proves the remote DB is updatable, and
the Make Table syntax is ok.
Copying the same Make Table to the problem PC and it fails.

I would agree that this suggests the local PC, but doesn't rule out any
permission problems on the remote db for the local user. What happens if you
copy the remote DB to the problem PC and run it there? (or just run the make
table within the local MDB)

 

[Paul]

I get the same issue with any local database - Select Query works fine,
but choosing a make-table query gives the error. The problem does not
lie with only one database file, or local vs remote access. The problem
started last Friday on this PC.

 

[JohnFol]

Can you add data to existing tables or create new ones manually? Just
wondering if it's problems with the ldb and file permissions / r/o
directory?

 

[JohnFol]

Hi Paul, another thought. If this is Office XP, then you are using ado,
rather than dao / rdo.
There are a couple of KB articles that point to a bug in Mdac., ie Q235390,
Q248076, Q245836

Not sure which version of mdac came with that version of access, but might
be worth installing the latest (2.8?)

 

[Paul]

Issue solved.

A token of my newness with Access - the issue appears to be with the
local .mdb file itself. What I thought were separate databases were
actually saved queries seen after opening a local database file. Some
of those queries were specifically talking to a remote database to
which I log into and the data returned was being saved to the one local
file. Other queries were run on the opened local file itself. The local
..mdb file was over 2 GB in size (!), and I could not even
Compact/repair it, nor reduce its size by deleting contents in order to
try compacting it.

A new database file has been created and I will watch its growth and
periodically compact it.

The 2GB issue is noted in Access' own help, so why couldn't MS get the
Invalid Argument error message to be more forthcoming over a known size
limit? Sheesh.

Thanks for your brainstorming.