Hi Mark,

Did you put the validation in an Insert and Update Trigger? The Trigger fires right before the record is Inserted/Updated. That should stop whoever is last in adding an offending record.

HTH,

>
>Whenever I enter start date and stop date for new record. This start and stop should not overlap
>with the dates of records which are already there in database.
>
>The problem is in multiuser situation. for example two users are entering new records at same time.
>both have entered same start/stop date. let's say 06/27/99 - 06/30/99.
>
>when User A goes to save this record, validation will check that is this range overlaps with any
>previous records? He will not get any previous records with this range because User B has not
>saved the changes yet. so He is allowed to save this record.
>
>This is ok. but By the time User A gets the results of his query and he saves the record. User B saves the record.
>so now, User A and User B both are allowed to save and database have duplicate entries.
>