I have always gotten around this, but keep meaning to post it as i found an additional quirk while working with tables recently.
1. When copying an existing report. (Report1, then copy via visual studio, then rename to report2), it never renames the class in the code behind to report2, causing an error. Not a big deal, just curious if there was a reason, or if it was sort of a bug. Not something new in Q1 2012, it's been doing it for a long time.
2. Never noticed this before Q1, but never worked with tables before Q1 either. When following same copy procedure as above, in report.designer.vb, the me.name="report1" does not change. An error is then shown in runtime (not in VS) that table1 is a duplicate or something along those lines. changing me.name="report2" fixes the problems.
Neither are deal breakers as they are easy to work around, just thought I would raise them.
1. When copying an existing report. (Report1, then copy via visual studio, then rename to report2), it never renames the class in the code behind to report2, causing an error. Not a big deal, just curious if there was a reason, or if it was sort of a bug. Not something new in Q1 2012, it's been doing it for a long time.
2. Never noticed this before Q1, but never worked with tables before Q1 either. When following same copy procedure as above, in report.designer.vb, the me.name="report1" does not change. An error is then shown in runtime (not in VS) that table1 is a duplicate or something along those lines. changing me.name="report2" fixes the problems.
Neither are deal breakers as they are easy to work around, just thought I would raise them.