Hullo again
I have another problem. A certain record is not being recognised by access as preexisting when running an update query to a table. Out of the odd fifty records, it keeps adding this one record when I rerun the query(which is done everytime a new record or edit takes place). This is despite the fact it has added it numerous times in the past, so I end up getting many many duplicates of this one record. i don't know why this is happening - as it is only one specific type of record it is happening to. Its screwing up the reliability of the whole db.

Please help me

Do you have a primary key in the table, or a useful unique index?

Perhaps more information about your update query, and what fields it affects on your table, and the values for this one record/type of record, will help.

David R

David

These are the fields that are updated to my main account transaction table. They originate from another query which calculates from a subaccount transaction table the amounts attributed to Business Area codes and ledger account codes and creates the first field the subaccountid.
1.[SubaccountID] - A unique text feild which includes concantenation of the fields[Reference], [A/c Code], [BusArea] & [function]. Because of this combination, there are no duplicates inthe first table.
2. [Reference] - this links the subaccount transactions to header table.
3. [A/cCOde] - Ledger Account
4. [BusArea]
5. [Function]
6. [2001-02] - all of the following numeric fields contain estimate entries
7. [2002-03]
8. [2003-04]
9. [2004-05]
10.[2005-06]
11.[2006-07]

I don't know if this helps - because the DB has a rather complex purpose to create budget financial statements on the basis of various program (subaccount) activity variations.
It has just decided to create havoc on one particular program update.
I was just wondering if anyone had had this sort of problem before.. with one record updating when it shouldn't.

Thanks for your time.

Why do you have separate fields for each year?

Rich
I attempted to have one column for the date of the estimate update (there is about three per year - governments have trouble making up their minds), one column for the amount and one column for the year the new amount realtes to, however this became increasingly complex for my forms and queries.
My users want the DB displayed similarly to other programs that this DB calculates for and feeds into, so that is why I have separated out the years to be estimated.
This shouldn't be the reason why I have this particular problem tho should it?

Thanks for your help, you guys have been life savers of late.