Invalid Argument - 3001
M. Perry
random places in the database. I have seen to come up from
variable assignments, record deletes, record appends, and
other actions in the database. If you debug and just press
continue (or F-5), it runs fine. The error message may pop
up again later, but it will at least run and properly
execute the code if you continue.
I have seen it happen on different databases on the
network here, but most often it happens on an Access 97
database.
I tried pulling the database completely local, but that
seemed to have no affect, as I still got the message.
I have compacted the database several times, also repaired
it, but the message persists. Anyone else get this?
Thanks,
Mike
Tony Toews
>My users are getting an error 3001 "Invalid Argument" at
>random places in the database. I have seen to come up from
>variable assignments, record deletes, record appends, and
>other actions in the database. If you debug and just press
>continue (or F-5), it runs fine. The error message may pop
>up again later, but it will at least run and properly
>execute the code if you continue.
From my page on this topic
http://www.granite.ab.ca/access/corruption/symptoms.htm and down
about 2/3rds of the way. There are embedded links in that paragraph.
"3001 - Invalid argument. This one typically happens when clicking on
a corrupted record within a table. Or by running a query or form
against that record. All the fields show #Error. See Damaged
record(s) within tables. Another cause may be missing Access 2000
SR-1 if you are trying to "import data, copy a table, or run an append
query." Also see You may receive an "Invalid argument" error message
when you run an append query in a large Access database file - 835416
which states that your MDB may be approaching the size limit."
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm