"Invalid Arguement" Message

[jamason07]

Good Morning,

I have a database that is being used by employees. When they attempted to open the form to do data entry, they recieved an "Invalid Arguement" message. When I researched the issue, I found a line in the data tables that had "#Error" for each column in the line. This was throwing off the database and was causing the error message. I was unable to delete the line and was forced to go to a backup and the clerks had to re-enter data since the tables were backed up the day prior. When I went into the tables and tried to delete the line, I would recieve the same "Invalid Arguement" error. This problem has occured twice in the past couple of months and I have to go to the backups to fix the problem. Can anyone tell me what is causing this and how to delete a line with "#Error". The "indians" are getting restless at the error and having to re-enter data after I go to the previous days back up tables. Thanks in advance!

JAM

 

[TheAceMan1]

Hoe are ya jamason07 . . . . .

In all my years I've never seen this problem . . So . .

Is the [blue]RecordSource[/blue] for the form Table or Query?

See Ya! . . . . . .

 

[jamason07]

The record source is a query. Initially I thought the query was the problem but the design was all good....very basic stuff. Then I went to the table and found the line and couldn't delete it. Ideas?

JAM

 

[TheAceMan1]

jamason07 . . . .

Hmmmmmmm . . . .

What OS?
What Version Acess?
DB is on network?

See Ya! . . . . . .

 

[RoyVidar]

I think this might be a corruption issue.

Did a search here, and found some links to threads containing information about similar challenges:

thread700-775648, thread700-728380

It is also mentioned in the Corruption symptoms page from Corrupt Microsoft Access MDBs FAQ.

There are some more information on corruption, how to avoid etc on that site.

Now, (as with TheAceMan1) I've never actually encountered this myself, but I've seen some creative ways of resolving the situation (preserving the other non corrupted records, I don't think deleting the corrupted record(s) works) here are two methods I'm lead to believe have worked under similar conditions:

* try to copy the whole table with data and structure. As I've understood it, the corrupt record(s) won't be copied, creating a new uncorrupted table
* use queries to copy all the information "above" (, "between") and "below" the corupted record(s) and append to a new table

Roy-Vidar

 

[TheAceMan1]

Hay Roy . . . . How are ya . . . .

I can't quite put my finger on it but my suspicions are that this is network related (maybe to many users at one time). The kicker is that this [blue]#Error[/blue] occurs in every field! Been researching myself. Found some things but they are not worthy of mention.

I was going to suggest [blue]importing all the objects into a new DB[/blue]. I've fixed a number of problems in the past this way. Was also going to syggest Compact & Repair, but I'm sure you know that doesn't always work.

In any case, I'm still curious what stats jamason07 will return on their system.

Good reaserch job Roy!

See Ya! . . . . . .

 

[jamason07]

Hey Guys...

Interesting reading. I did read something about being next to a radio transmitter and stray waves. In actuality....the main computer sets next to multiple radios. I'd hate to think that this is causing my problems because there is no way around that one.

As far as salvaging the data...I've tried exporting to excel so I could import the fixed data. That didn't work. I'll try copying the data as you guys mentioned. I would hate to have to copy the entire database to a new one due to all the other tables, queries, etc. But that may be what has to happen.

Anyway...thanks for the research guys. This is some good stuff to work from.

V/R

JAM

 

[jamason07]

OK...some updated info. I've tried copying the table and it won't even let me do that. I've tried to open it via the table directly and through the query and still can't get to the data to see it. I think I'm screwed on this one. Fortunately I've got a back up. I may have to rejoin the front and back end and only allow one user. I've talked to the user and it occured again when multiple users were in just like last time. Oh well....time to start copying down back ups! Thanks!

JAM

 

[TheAceMan1]

jamason07 . . . .

[blue]I would hate to have to copy the entire database to a new one due to all the other tables, queries, etc. But that may be what has to happen[/blue]

If you [blue]import[/blue] into a new DB, you can do it all in one shot.Once for the backend and once for the frontend. When importing the frontend you can set it up to import every object (all queries, forms, reports, macros, ect . . . everything).

You could import the backend first and see if that takes care of the problem (you'd only have to relink the tables). You could save the old backend, use the new, load up with users and see if the problem returns . . . .

Goodluck . . . and good hunting . . . .

See Ya! . . . . . .