There have been some fundamental changes that are really hurting us in converting from 2007 > 2011.
I am at a loss to know whether this is our issue or the upgrade but I have code that has worked for several years suddenly break during this tranistion.
Two specific examples:
SQLFetch1 to init cursor, SInsert1 a record, then immediately SUpdate that record and it blows up in that charming (try-catch? hahaha) SL fashion and kills the screen.
Screen with level 0 key and level 1 details grid. Grid setup also loads a nolevel table to retrieve the name associated with a foreign key on the level 1 table. Works great... until you save, then you get another blowout event similar
Again, logic that worked perfectly for years through updates from 5.5 to 2007 to 2007 SP3. I see no mention in the VBTools update docs that would explain this although I will allow I might have missed something.
Background: SQL 2008 at level 90 compat., No custom triggers
Any thoughts welcome,
My opinions, don't associate with anybody else, etc. etc. :)
Just applied SP1. Fixed both issues I listed. Grateful for that!
However... didn't see anything in the release notes about related modfications to either VBtools or the API dlls. I wonder what else they changed?
Other Microsoft Sites
I'm a Customer
I'm a Partner
Use the official Twitter tags:
#MSDYNCOMM | #CONV13