Hello!
I am using .BeginTrans, .CommitTrans, etc., extensively in an application.
Works great. Now I am trying to run the application with connections to
different data providers. So far, it works great with a local MSJet4 file
(.mdb) or with the file on another Windows server on the LAN.
Now I want to use the "MS Remote" (RDS) connection provider to that same
file on another computer. It seems that transactions are not sup****ted
with
MS Remote when I use an ODBC Data Source (in this case, a System DSN to an
Access 2000 file). Everything else works great except for the error
"Transactions are not sup****ted by the Remote Provider."
Is this an issue with MS Remote (RDS)? Or might this work with a remote
provider other than ODBC? Do any of the other OLEDB providers sup****t
transactions through the "MS Remote" connection provider? I tried the Jet
OLEDB provider as the remote provider, but the app did not work at all
because the SQL command strings of type adStoredProc no longer worked with
the stored queries in the mdb file. If I had figured that one out, would
the transactions have worked then?
What other options might I consider? Should I learn to write a custom
business object that acts like the default data factory, but which
sup****ts
transactions as a method somehow? (I've never written a business object
before.) Is there an excellent tutorial somewhere? Sometimes I think
Microsoft is intent upon suppressing productivity in this regard. Does
anyone have a "Hello World" for a custom business object?
(Rewriting the whole app for .NET is not an option: It work too well to
screw it up now. Besides, it's just way too big and uses every
"VB6-but-not-VB.NET" technique in the book.)
Any ideas? I would be especially grateful!
- Jim Rodgers
|
