Reporting Visual Studio: ShowGrid is not working
In Visual Studio
Tools -> Option -> Windows Forms Designer -> General the Settings are
But there is no visible Grid.
Upvotes: 79<=-=Jul 22 2008 1:26PM=-=>
Thank you for providing this feedback. With SQL Server 2008 we replaced grid lines with object snapping and snap lines. We will consider this as feedback that you would like grid lines back. We will consider adding them back in a future release. If this feature is brought back, however, it would not be enabled by this VS option, the Designer would have it’s own command to display or hide grid lines. The VS option you mention is for designing WinForms apps, not directly related to the Report Designer.<=-=Jul 23 2008 2:04AM=-=>
Many thanks for your reply!
I would also like the SnapToGrid, DrawGrid, and GridSpacing options back. Report development is so much more cumbersome with the object snapping and snap lines. I could actually see how things lined up when the grid was there. Now I’m just guessing. This is a step backwords in usuability. I would say have both options availble to the user to choose which one they like, don’t get rid of the time tested way of doing it that was present in SQL 2000 Reporting Services and SQL 2005 Reporting Services!!!<=-=Dec 12 2008 6:43AM=-=>
I would also like to comment that I have a report with say 100 text boxes on it, and getting them all to line up properly is a very time consuming task in SQL 2008 Reporting Services. This was so much easier with the grid options in SQL 2000 and SQL 2008. This new version requires such fine motor skills that I spend hours aligning things properly. And I have to do it textbox by textbox because Microsoft removed the ability to multi-select text boxes with the mouse. This is such a disappointment<=-=Feb 2 2009 9:55AM=-=>
I agree that this is a large step backwards in usability. The snap-to lines are not granular enough and using ctrl + arrow makes it very difficult to line things up. We usually had our gridlines set to .0625 in BIDS 2005.<=-=Dec 31 2009 8:59AM=-=>
I’ve been using Visual Studio since 1996. This is the first time I’ve used the Report Designer for SSRS, and I have to say it’s the worst designer I’ve ever used from Microsoft. It’s a piece of crap. I’ve never spent so much frustrating, useless time trying to twiddle little UI items around trying to get them right. Business users are VERY PICKY about how their reports look.
Forms designers generally have snap-to, and grids, and options to ALWAYS show the ruler because they are extremely useful tools.
The individual(s) who decided to “replace” design features instead of “enhancing” design features should be taken out to the proverbial wood-shed for an “attitude adjustment”…
I echo silverfox1948 sentiments exactly.<=-=Apr 15 2010 8:13AM=-=>
Also agree with silverfox1948.
I have to go back to 2005. This is entirely unacceptable.<=-=Jul 9 2010 12:51PM=-=>
Agreed. We are also putting a halt to 2008 SSRS development unless/until this functionality is restored. How can you have a report designer without this functionality? Why would you remove functionality that works? It makes no sense.<=-=Aug 3 2010 11:04AM=-=>
Folks at “Microstop” have put the screws to all report designers using MS SSRS! Why in hell would something as useful and critical to report design as grids be left out??? That is a huge boneheaded decision. Anyone with exacting requirements will be forced to abandon MS report designers in favor of competitor’s tools or take a step back and deal with all the crazy compatability issues maintaining multiple development platforms. What a pain in the ass!
MICROSOFT – FIX THIS NOW!
Another thing that has been botched from 2005 to 2008. This is extremely painful to line report elements up. And I don’t have syntax highlighting for MDX queries. Why take existing functionality and remove it? Don’t remove helpful things to developers because it makes the release date easier.<=-=Aug 5 2010 12:54PM=-=>
I hope someone at Microsoft really reads these comments.
I used to brag about how easy it was to lay out reports for SSRS, compared to other designers I’ve used. I recommended it to others with enthusiasm.
Now, because of the changes to the layout controls (removal of the snap-to-grid), not only can I no longer recommend the product, but I dread having to use it myself.
I hope the feature can be resurrected.<=-=Aug 6 2010 1:46AM=-=>
I agree with all of the above. Add the functionality back. Poor, poor decision. I have a very hard time understanding why removing functionality is considered a step forward.<=-=Aug 9 2010 6:21AM=-=>
silverfox1948 has it right!
I, too, find the lack of grid lines perplexing, annoying, and frustrating. Why would you remove existing, vital functionality?
In addition, the menu option appears to turn grid lines on (ShowGird=True), but actually doesn’t work.
Microsoft, please restore the option to display gridlines!<=-=Dec 6 2010 4:10AM=-=>
I have to go back to VS2005 for designing reports, like many others. The report designer of VS2008 and VS2010 is unusable if you place more than one item on a report. But I have to design reports with multiple pages… Even the report designer of Access 2 (more than 15 year old!) works like a charm, compared to this desaster.
give us back
the grid snap!
Is this yet another feature that has been removed so that it can be sold back to us as an “improvement” in the next release version?
Bill Gates did say back in ‘95 that this was one of the ways MS made boatloads of money. Mind you it isn’t the idea of the nice developers, but that of the the evil greedy sales force.
Please show me that my cynicism is unfounded!
It turns out Luddites don’t know how to use software properly, so you should look into that. — The reason we come up with new versions is not to fix bugs. It’s absolutely not. It’s the stupidest reason to buy a new version I ever heard. When we do a new version we put in lots of new things that people are asking for. And so, in no sense, is stability a reason to move to a new version. It’s never a reason.
I’ll have to defend Microsoft on this one: The object-snap feature is a very clever one, and I loved it instantaneously when I first met it – when was it? MFC in VS 2003? Earlier? I still admire the intelligence behind it, and this same intelligence does its job in SSRS BIDS 2008.
However, as can clearly be seen by the amount of bad karma generated, we report designers do want the grid back. In my humble personal opinion the grid way of alignment is better overall, even after taking into account a certain illogical reluctance to learn and some unfounded stubbornness. Layout metrics are not only about pleasing the eye.
Some points to ponder:
- in the new BIDS, you can no longer apply a numeric value for coordinates of a multi-selection, where you could in 2005.
- enforcing the illogical wish that all columns in a table be integer multiples of a SI unit is now both harder and easier than before (Mark column enter width? Nope. BIDS changing the width just entered to the nearest inch-synced off-grid value? Nope!) – not all is lost.
- In my experience there have always been slight rounding error-related issues in SSRS. Usually, those are solvable by sticking to multiples of the base unit (not easy for metric system people). This gets harder without grid-snap.
- In 2005, it was trivial to place a control at coordinate zero. In 2008R2, not simply hard, but impossible to do in one step.
- 2008R2 no longer remembers my wish to turn on rulers. A trifle, but yet another grain of sand in the quest for a uniform layout.
Concluding, I think there simply has been no usability testing. If asked in a quiet moment, I will tell anybody willing to listen that 2008R2 is a way better product than 2005 was, and do so with gusto. Then why is it driving me nuts every time I have to work with it? Because there’s no end to those trivial tiny trifles that seem so unneccessary.<=-=Aug 17 2011 11:24AM=-=>
I agree with Robert that object snapping is a nice feature, and I absolutely love using it when laying out windows and web forms. However, when I’m designing a report I’m not try to make objects line up with other objects on the report; I’m trying to make objects line up with every other report we have! Snap-to-grid was great for this, whereas snap lines don’t help at all.
PLEASE add this back in! Snap-lines are NOT the same as snap-to-grid!<=-=Nov 11 2011 11:37AM=-=>
Adding another voice to the choir on this. This is an absurd step backwards for SSRS 2008.<=-=Nov 11 2011 11:37AM=-=>
Adding another voice to the choir on this. This is an absurd step backwards for SSRS 2008.<=-=Nov 23 2011 7:40AM=-=>
Yes this is causing real pain to me too, pls sort it asap!<=-=Jan 3 2012 9:11AM=-=>
No snap-to-grid feature in a reporting solution, seriously?<=-=Jan 19 2012 9:07AM=-=>
My IT department switched to from 2005 to 2008 R2 recently and we are all disgusted with the removal of the snap-to-grid feature in the BIDS designer. We are having to go back to VS2005 to design reports, then port them over to 2008 to take advantage of new features. I echo the requests below to bring back the grid snapping. It’s been an essential part of an IDE as long as I can remember… who thought it was a good idea to remove?<=-=Mar 13 2012 8:06AM=-=>
Wow – the grid/snap issue is 4 years old and unresolved.
The object snapping is inaccurate. Maybe at least THAT could have been fixed by now.
And the fact that object snapping doesn’t wo