locked
invalid argument RRS feed

  • Question

  • I am getting an "Invalid Argument" error when trying to open a table that we have used for years.  Since it won't let me open the table to see what data may be giving it the error, I am stuck.  I am running MS Access 2003.

    Thanks

    Thursday, July 15, 2010 9:05 PM

Answers

  • Curt Ch wrote:

    I am getting an "Invalid Argument" error when trying to open a table that
    we have used for years.  Since it won't let me open the table to see
    what data may be giving it the error, I am stuck.  I am running MS
    Access 2003.

    Have you tried Compact/Repair? Menu Tools - Database Utilities.


    Peter Doering [MVP Access]

    • Marked as answer by Curt Ch Monday, July 19, 2010 5:56 PM
    Thursday, July 15, 2010 11:26 PM

All replies

  • Curt Ch wrote:

    I am getting an "Invalid Argument" error when trying to open a table that
    we have used for years.  Since it won't let me open the table to see
    what data may be giving it the error, I am stuck.  I am running MS
    Access 2003.

    Have you tried Compact/Repair? Menu Tools - Database Utilities.


    Peter Doering [MVP Access]

    • Marked as answer by Curt Ch Monday, July 19, 2010 5:56 PM
    Thursday, July 15, 2010 11:26 PM
  • Hi Curt
     
    Curt Ch wrote:
    > I am getting an "Invalid Argument" error when trying to open a table that
    > we have used for years. Since it won't let me open the table to see what
    > data may be giving it the error, I am stuck. I am running MS Access
    > 2003.
     
    Are you sure you are opening a table, not a query? A table doesn't have
    arguments...
     
    Try to connect to this table from another application and access the data
    from there.
    Or open the table in design view and check all the properties (validation
    properties mainly) for all fields and the table itself.
     
    Henry
     
     

    [MVP Office Access]
    Friday, July 16, 2010 5:08 AM
  • There are a number of components to a table -- each of which can cause problems.

    See if you can use the Database Documenter to list all of the properties, indexes and fields (along with their properties) for the table.  It is possible that one of them has a bad reference (i.e. a reference to a lookup table that no longer exists).

    If the Database Documentor won't run dump the properties you can do it in code by walking the fields collection and for each field the properties collection.

    Friday, July 16, 2010 6:38 AM