> Ok it seems to me the way I am understanding
> cftransaction is that it rolls back the transaction
> only per database? Is that right? If it is that is
> kind of worthless since I have a few different
> databases that are hinging upon one databases fields
> being filled in.
You're correct. CFTRANSACTION only works within one ODBC datasource. Since
it relies on locking within the database itself, that's not a big surprise.
In most cases, your application's database should contain all of the tables
it needs. In cases where it makes sense to use separate databases, you can
use the Distributed Transaction Coordinator in Windows NT/2000. DTC allows
you to execute distributed transactions across multiple databases.
Typically, you'd use distributed transactions from within an SQL Server
stored procedure, or from a COM object that can communicate directly with
both databases.
If you're using several MS Access databases, you might be able to link
tables from one within another, which would get you the same effect. You'd
simply direct your queries to one ODBC datasource in that case.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
