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). I
won't get paid unless I can make an existing app to go across the Internet
to get the data. So far everything works great except "Transactions are
not
sup****ted by the Remote Provider."
Is this an issue with MS Remote (RDS), or might this work with a different
remote provider than ODBC? For example do any of the OLEDB providers
sup****t transactions through MS Remote?
What other options might I consider? Could I 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? Microsoft seems intent upon suppressing
productivity in this regard.
Rewriting the whole app for .NET is not an option: It's just way too big
and uses every "VB6-but-not-VB.NET" technique in the book.
Any ideas?
