> 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