HI. very disturbing problem. I have an Order Table [OrderID] attached to an OrderProcess Table [OrderProcessID]. Users always create duplicates OrderProcess, sometimes two to three duplicated OrderProcess ID [blanks included] . This caused confusion in the Order Processing Dept. Any "bullet-proof" codes to prevent this?

Hi,

What is considered a "duplicate?" How do the users manage to create them? Are you using a form for data entry?

Just my 2 cents... (IMG:style_emoticons/default/2cents.gif)

HI DBguy. Yes I have a frmOrderProcess linked to frmOrder via OrderID. User create a frmOrderProcess from a commandbutton in the frmOrder. I transferred the OrderID from the frmOrder into the frmOrderProcess. User without knowing there is a form already opened create another blank form with the same OrderID, thus a duplicate. is created. Possible to have codes to check whether OrderID in tblOrderProcess is greater than 1?

You mean something like?

If DCount("*", "tblOrderProcess", "OrderID=" & Me.OrderID)>0 Then
'duplicate
Else
'new
End If

Just my 2 cents... (IMG:style_emoticons/default/2cents.gif)

Hi DBguy, Thats what I want, simple and sweet. Thanks again.

Hi,

(IMG:style_emoticons/default/yw.gif)

Glad we could help. Good luck with your project.

you could also add a unique key to the orders table, then access will prevent duplicates being inserted

That's interesting, how do you add a unique key to the Order Table to prevent duplicates? Appreciate your help.