Invalid Argument, Please help!

  • Thread starter Thread starter Stockwell43
  • Start date Start date
S

Stockwell43

Hello,

Can someone please tell me what it means when I go on a record and I get a
pop up saying "Invalid Arugument" and all the text is Chinese?

Thanks!!
 
Hi,
if you have any memo fields in the record, it could be related to using a
memo field.
Otherwise it sounds like corruption.

Here is a post on fixing corruption from Allen Browne.

A decompile might be in order here.

Here's a standard sequence for sorting out a raft of possible issues. Try it
in order:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
In Access 2007, it's:
Office Button | Access Options | Current Database | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access (holding down the Shift key if you have any startup code),
and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

7. Still in the code window, choose Options on the Tools menu. On the
General tab, make sure Error Trapping is set to:
Break on Unhandled Errors
and the Compile on Demand is unchecked.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, reference ambiguities are resolved,
the code syntax is compilable, and the VBA options are set to show errors
and avoid this kind of corruption.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

Jeanette Cunningham
 
Hi Jeanette,

Thank you for your reply. I will surely give this a shot. Funny, I have
built many databases and never had this problem before. I guess there's a
first for evertything right? :o)

Thank again, I appreciate your help!!
 
Back
Top