S
SUZYQ
We recently upgraded to Access 2003 and have started getting the "3001
Invalid Argument" error frequently. Often it has to do when we are
working with Oracle tables via an ODBC connection.
Our stats: Windows XP, Office 2003, Jet 4.0.8618.0 (this seems to be
even newer than Jet 4.0 SP8?).
The databases do reside on a server.
What's also wierd is that even when we work with the databases in a
terminal services environment that is running Access 2002 we're getting
the same error.
I've read many postings that talk about compacting and repairing the
database and the size of the database. The databases I'm working with
are nowhere near the max 2GB size (all are under 500MB).
Often, if I am given the option to click debug when I get the error and
press "F5", the code will then continue to run past the point it
stopped.
The other time I've been getting the error is when filtering an Access
table (not via ODBC). I'll click to run the filter button, get the
error, and then when I click the filter button again it'll run.
Help!
Invalid Argument" error frequently. Often it has to do when we are
working with Oracle tables via an ODBC connection.
Our stats: Windows XP, Office 2003, Jet 4.0.8618.0 (this seems to be
even newer than Jet 4.0 SP8?).
The databases do reside on a server.
What's also wierd is that even when we work with the databases in a
terminal services environment that is running Access 2002 we're getting
the same error.
I've read many postings that talk about compacting and repairing the
database and the size of the database. The databases I'm working with
are nowhere near the max 2GB size (all are under 500MB).
Often, if I am given the option to click debug when I get the error and
press "F5", the code will then continue to run past the point it
stopped.
The other time I've been getting the error is when filtering an Access
table (not via ODBC). I'll click to run the filter button, get the
error, and then when I click the filter button again it'll run.
Help!