Got pop-up error "Invalid Argument" when using UPDATE query in MS Access 2010

Hi,

I am using a MS Access 2010 DB that was upgraded from MS Access 2007.

When I run a simple UPDATE query (e.g. as follows) that works fine in MS Access 2007 version, I get the pop-up error message "Invalid Argument".
Code:
 
UPDATE [Store List] SET [Store List].Manager = "John"
WHERE ((([Store List].Manager)="Mike"));
The database is well below the 2GB limit.

Another weird phenomenon is: when I manually change some values using copy-paste upon the table, the error "Invalid Argument" pops up too; if I ignore it and continue pasting the new values, the update can be done.

How to deal with this issue?

Thanks in advance.
 

Question Info


Last updated October 28, 2019 Views 4,397 Applies to:

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Is the manager field a 'Lookup' field?  If so then it probably contains numbers instead of text.
Build a little, test a little

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you KARL DEWEY.

 

The manager field is not a 'lookup' field ...

 

 

 

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Design the table. Inspect the Validation Rule properties for each field.

Also be sure there are no Data Macros defined.

Open the Relationship window. Inspect the relations to this table. Anything funny?

Did you compact the database?

 

-Tom.
Microsoft Access MVP
Phoenix, AZ

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you Tom van Stiphout.

 

No Validation Rules.

No ralations to other tables.

Not compact the database.

 

It is weird because it works well with MS Access 2007.

 

But MS Access 2010 ...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

You should compact the database.

I still feel this SQL statement is completely valid. If it continues to act up, I might export everything to a new database.

-Tom.
Microsoft Access MVP
Phoenix, AZ

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Go to the VBA Window.

Go to DEBUG

Click COMPILE

 

Sometimes errors that it finds can actually be the cause of the problem when it doesn't seem logical.

 

If, when you do what I said up above, it gives you an error, it will highlight it.  Fix that error and then do the same thing again until you have no more errors.

-----
Microsoft Access MVP 2008, 2009, 2011
If a post was helpful click the FOUND THIS HELPFUL link

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thank you boblarson.

 

I tried but no use.

 

Other databases don't have the similar problem...

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Has anyone ever found a solution?  I am having the same error with a freshly created table.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I am having the same problem. It doesn't make sense - yet.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

I've worked with MS access for about fifteen years and haven't seen this error in awhile - in Access 2003 it meant that the database was approaching critical size.

I'm getting this error when writing queries in databases that I've established that use data imported from another system.  The files are big (12k records) but not more than Access can typically handle.  Some of the fields have numeric/special character names (for instance, 1-Name, 2-Address, 3-Phone).

The database will work fine for awhile and then suddenly a perfectly straightforward update query will pop up with an "invalid argument" error.

In the same database, when I try to manipulate my imported tables, such as deleting a field and its data, or concatenating fields to a new field, I get strange errors that imply that the database is corrupt.  For instance, I will write a query using the table and get an error that the query can't find a field that never existed in the table (but that does exist in another table in the database.)

I suspect the two issues are related.

Compacting the database does not help.  Restarting access does not help. 

The VBA compile idea is interesting, but since there are no projects in the database, I don't know how (or whether) to do this.

The only thing so far that has worked is to copy the data into excel and re-import it into a new database.  Painful, since I've had to do that three times in as many weeks.  This time I'm going to try renaming the columns on the table that keeps breaking and see if that makes a difference.

3 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.