September 4, 2012 at 6:41 am
Nice question Sreepathi, Thanx for the easy point
September 4, 2012 at 6:59 am
Excellent question. I remember this causing me a great deal of confusion when I first ran into it.
September 4, 2012 at 8:35 am
September 4, 2012 at 9:03 am
Not all the rules have an exception, unless you use table variables in transactions
I'm glad I did my homework about table variables when I studied that theme.
September 4, 2012 at 9:15 am
Do you want to laugth at someone? Well, here you have the opportunity: I got it wrong because for me 2005 and 2012 were "date", not money and because the second one was null, so the answer I choose, was zero
I don't drink coffee... maybe I should start
September 4, 2012 at 9:51 am
Nice question
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 4, 2012 at 10:23 am
Great question!
Rob Schripsema
Propack, Inc.
September 4, 2012 at 6:01 pm
Nice question, was doing too many things at once and chose the wrong answer. Doh!
September 5, 2012 at 4:06 am
Very good question. Thanks.
September 5, 2012 at 6:38 pm
Great question - was not aware of that issue with SQL variables at all. Leanred something very important this morning!:cool:
September 5, 2012 at 7:26 pm
Wrong here. Probably because I don't know anything about table variables, or try/catch for that matter. One of these days I'll move beyond Visual FoxPro 6.
September 5, 2012 at 10:52 pm
Very good question, thanks.
September 6, 2012 at 4:57 am
Mainly...........
The "ROLLBACK TRANSACTION" does not work with table variables.
Viewing 13 posts - 16 through 27 (of 27 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy