> Thanks for the clarification on Access, I believe you're
> right since it's not a truly relational product.
I don't think that's really the reason, though, but rather that its locking
is less granular than SQL Server's or Oracle's.
> However, I always use CFTry and CFCatch with Inserts and
>
2 11:34 AM
To: CF-Talk
Subject: RE: Inserting and CFTransaction
> Access doesn't have any good way to prevent the multiple
> simultaneous insert problem. So, by using CFCatch, and
> CFTransaction you can catch the error of the second insert,
> rollback the changes and
> Access doesn't have any good way to prevent the multiple
> simultaneous insert problem. So, by using CFCatch, and
> CFTransaction you can catch the error of the second insert,
> rollback the changes and try again with a new value.
> CFTransaction seems to suggest that your set of queries
> w
fice: (800) 604-5227
Cell: (407) 491-9848
-Original Message-
From: Rick Walters [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 15, 2002 10:48 AM
To: CF-Talk
Subject: RE: Inserting and CFTransaction
It seems that many problems I see in this list revolve around
determining
the next record
It seems that many problems I see in this list revolve around determining
the next record for an insert and methods to use cftransaction as a form of
database locking to achieve this purpose. So, I figured I would add two
cents that might help some of you.
First, what you can do is determined
5 matches
Mail list logo
