Ryan Whitaker - All Comments

re: Transactions with TableAdapters, a lazy man's approach

Rob Orchiston — Wed, 16 Sep 2009 18:41:02 GMT

Yep, this works awesome! Thanks.

re: Transactions with TableAdapters, a lazy man's approach

Pete — Fri, 07 Aug 2009 09:38:44 GMT

Works like a charm!

re: Modify data before it's inserted in SQL Server 2000/2005

ilias — Tue, 14 Jul 2009 07:13:59 GMT

Waylon is right, the trigger will fail when more than one records are inserted / updated... The problem is the

SET @x = (SELECT x FROM INSERTED)

INSERTED will contain multiple records when the insert/update statement affects more than just one record

re: Transactions with TableAdapters, a lazy man's approach

TD — Wed, 10 Jun 2009 19:09:48 GMT

Seems like you are going through a lot of trouble to get the connection off the table adapter passed in. why not just make the connection modifer public and would that not bypass the need to use reflecttion at the TA connection level? If the connection is public, all you have to do is call the begintrans to get the sql trans object.

As for the internal commands, I don't use them anyway.

Then, I would suggest creating a generic table adapter that all table adapters would inherit from. You can see the base class property in all table adapters in the designer, just set the base there.

The generic table adapter should provide a means for setting a transaction to all internal commands.

This would be my approach if it helps...

re: Transactions with TableAdapters, a lazy man's approach

TD — Wed, 10 Jun 2009 18:54:00 GMT

Byval and byref are retarded for VB only. Byval means nothing with object (ref) types. Understand the stack vs. heap

re: Transactions with TableAdapters, a lazy man's approach

Matt C — Fri, 06 Mar 2009 14:44:35 GMT

Just a quick follow-up...

Is there any reason why, in your TableAdapterHelper class, all the parameters to the functions could not be passed by Reference instead of by Value? In fact, unless I am missing something, this might even be a preferable approach, to save passing copies of TableAdapter and Transaction objects around all over the place.

Am I right or wrong?

re: Transactions with TableAdapters, a lazy man's approach

Matt C — Wed, 04 Mar 2009 17:22:32 GMT

Just another addition to the testimonials by other posters, above...

Thank you very much for this code, it's great - exactly what I needed. I also agree with you when you say this is probably the best way to implement transactions with Table Adapters.

Thanks!

?????????????? ?????????????????????????? … » ?????????? ?????????? » .NET: ???????????????????? ???????????????????????? ?? ???????????????????????????? ???????????????????????????? DataSet.

Fri, 27 Feb 2009 07:17:46 GMT

Pingback from ?????????????? ?????????????????????????? … » ?????????? ?????????? » .NET: ???????????????????? ???????????????????????? ?? ???????????????????????????? ???????????????????????????? DataSet.

re: Modify data before it's inserted in SQL Server 2000/2005

Hernan — Tue, 17 Feb 2009 22:09:56 GMT

you can use table variables... @table

re: Transactions with TableAdapters, a lazy man's approach

grobanderson — Wed, 29 Oct 2008 11:13:03 GMT

It seems it doesn't work on Oracle ODBC:

message is

"ERROR [HYC00] [Oracle][ODBC]Optional feature not implemented."

Someone help me!!