Need Query over Come 'Invalid Arguments' Error

Ashfaque

Search Beautiful Girls from your town for night
Local time
Today, 08:26
Joined
Sep 6, 2004
Messages
897
Hi,

I have a table SSR (Sample Supply Request) with around 10,000 records. Let us say it has following 4 fields along with their field types.

A -Date
B -Text
C -Number
D -Memo
E -Yes/No

Due to the write-confilict, it stored one of the records as error, error, error in each field of recordset.

Let us say this error replaced record no. 5530. Rest records are ok.

The problem is who ever user reach to this table through forms, it produced error "Invalid Arguments" and stop doing nothing.

To come over this problem, I open the table itself I do copy structure of the table to create a new table. Then copy (manually) preceding 5529 records leaving record # 5530 and then rest of the records to the new table. Later on I do delete the infected table and rename the new one to its old name preserving relationship. But I am fed-up doing this.

Although its a matter of little time to spend doing this but I believe it is not the correct way.

Can anyone tell me if there is any kind query I can write to copy all records except the damaged one to the new table?

Suggestions are welcome....

With kind regards,
Ashfaque
 
Ashfaque said:
Can anyone tell me if there is any kind query I can write to copy all records except the damaged one to the new table?

Can't you just delete the damaged record?
 
The problem you need to address is not how to correct the problem but how to prevent it.

It is caused because you allow more than one person to add/edit the same record, thus Access gets confused and thus it puts up the shutters and stuffs the complete record.

What you are doing in copying records and then deleting original table is only way I know to fix.

To prevent it happening in the first place you must have a record locking strategy.

The properties of your add/edit/view record for has an item Record Locks.

This is probably set to No Locks thus the door is wide open

Change it to Edited Record.

Thus when someone has the record open for editing everybody else will be locked out of that record for edit. Problem resolved for the future

HTH

Len B
 
Things that I have read indicate the problem revolves around the memo field. You might be able to resolve the problem by segregating the memo field in a separate table. You can join the two tables in a single query and use that to replace the original table in any RecordSources.
 
Thanks for the valuable advices.

I would like to answer as follows;

Thanks Stephen81.

I can not even move over the damaged record. As soon as control reach even closer to damaged records, starts giving massgages "Invalid Arguments".

Thanks Len Boorman.

I will check with your idea to make Record Edited.


Thanks Pat Hartman,

Do you mean that I should keep only memo field in a separate table that will be related with prime table?

I have more than 50 fields in table SSR and already there is another table called SSR_Stages. both are related with each other based on one-to-many relation ship.The Memo field is in parent table. This is the original situation.
The Error problem occurs in parent table only not in SSR_Stages table.

In this case, will it be possible to create another table? And what relationship I would have to maintain? one-to-one?

Please advise.

With kind regards,

Ashfaque
 
Last edited:
Yes, the relationship would automatically be defined as 1-1 since both primary keys would be the same and that is how the tables would be linked.

I can't promise that this will resolve the problem. It is based on something I read some time ago and can't lay my hands on. Try searching the knowledgebase to see if anything there helps.

I attached a word doc that has some info that might be helpful. Some of the links don't work, I'm sorry. I don't know where I copied the file from.
 

Attachments

Users who are viewing this thread

Back
Top Bottom