"Invalid Argument" - 2gb isn't the problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jdircksen
    New Member
    • Jul 2006
    • 2

    "Invalid Argument" - 2gb isn't the problem

    I have a table that keeps crashing. The only error message I get is "Invalid Argument". Each time, a single record will turn into "#Error". Each field says this in the row. When this happens, Access won't let me delete just that row, so I end up having to copy and paste all records into Excel (it won't let me export), deleting the #Error row, then importing it back into Access. It is a pain because I lose the data from that row and I have to fudge the records so I can re-autonumber them all.

    Any ideas?
  • PEB
    Recognized Expert Top Contributor
    • Aug 2006
    • 1418

    #2
    This maybe due to simultaneous change of the record by many users that saved their changes!
    I've had one time this exerience and this was the story!

    Comment

    • hemiras
      New Member
      • Nov 2006
      • 1

      #3
      i also have same error but to me even i just paste the data into the table it still says that error message and even changing the field size, what would be the error?

      thanks

      Comment

      • Killer42
        Recognized Expert Expert
        • Oct 2006
        • 8429

        #4
        Just a question - have you tried compact/repair?

        Comment

        • NeoPa
          Recognized Expert Moderator MVP
          • Oct 2006
          • 32633

          #5
          I've had this problem before.
          It turned out to be that some of the data within some of the records (all those with #Error values) was invalid for the field.
          In my case I was linking via ODBC so I hadn't entered the data via the Access interface at all.
          My back-end system had a special value of 99999999 for expiry dates that didn't need to expire.

          Comment

          • PEB
            Recognized Expert Top Contributor
            • Aug 2006
            • 1418

            #6
            But sometimes in Access this arrives also..

            In one form which has Before update event procedure and after update evewnt procedure.. Also the form has before insert one...

            And when the two procedures are driven together I'm obtaining this kind of error!

            You introduce your data from a form as i understood?

            Can u tell us what is the coding in your form? Is there some contredictions like Before update and Before insert that runs together and possible slowing of Before Update?

            Comment

            Working...