Hia Alan,

I check the entryid in case it's an update trigger. Don't want it
failing because it overlaps with itself!!

It does see all committed records, but I'm worried about uncommitted
ones! Two users could add records in seperate transactions, not see
the other new addition, both commit. And bingo, you've for
overlapping data!

John

--- In firebird-support@yahoogroups.com, "Alan McDonald" <alan@m...>
wrote:

> > Well, it's a option in SQL Server 2005 (turned off by default!).

For

> > use when 'update conflicts are rare' according to the blurb.
> > Maintained by using a linked list in tempdb (ewwwwww!).
> >
> > I'm prepared to accept FB is the coolest db ever! but...
> >
> > Just tell me how I can solve my period-overlap problem???!?!?! :0
> >
> > John
>
> Why is there an overlap problem? Your trigger should work on all

committed

> work. Or raise an exception if there is a conflict. but why do you

check the

> entryid? it's unique isn't it?
> Alan