Hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it, hate it.
Stupid piece of shit, I hate it. Fucking hate it. Every goddamned moron involved in the making of this piece of shit needs to be raped by goats, with Pan himself acting as the fluffer.
Hate it.
This public service announcement has been brought to you by a months worth of frustration with this progams “idiosyncracies” and inability to do even the most basic of things (like its inability to put report fields in headers or footers). Thank you.
Pttttttttttt. I’m putting together a website and trying to get FrontPage and VisualStudio.NET to play nice together. I’m succeeding (so far), but damn it has been a royal pain in the ass!
Can somebody* explain to me why the fuck it is SOOOOO wrong to put fields in report headers/footers?
Can somebody explain to me why the stupid idiotic piece of shit program does NOT recognize “landscape” as a viable, “hey I want to do this ALL the time rather than setting my print setup properties EVERY GODDAMNED TIME I WANT TO PRINT OUT A GODDAMNED TEST PAGE???” alternative? Even if you tell it that the report body is 11X8.5, it’ll still print portrait-style - 8.5X11.
And I love the crashes. Oh, I just love the crashes.
Can somebody explain to me why the column function works like shit? I have a basic two-column report. I want the items centered just… so and have no problem getting it correct.
But just on the left column of page 1. Whatever I do, I can’t get the right column in page 1, or the rest of the columns in the following pages to look like the left column in page 1.
Goddamned piece of shit.
Would it have been so impossible to program a goddamned zoom function in the Layout tab (which is where you get to design your reports). You get the zoom in Print Preview, but not when you’re designing your reports. Has the thought ever occurred to the dipshits at Microsoft that when you’re drawing lines, you might want to zoom in a bit?
*I didn’t want to use your name: no need to make it sound as if I’m yelling at you, Ponder.
And after that, try Oracle Reports. You have to do like 5 different things, in the proper order, to just move a field around if it’s in a tight location. And that’s on a good day.
Ummm, perhaps this thread would get more responses if you would explain what all is going on for individuals that aren’t as well versed in all of the technological terms.
I think you’re pitting Microsoft’s new software development tools, or something, but I’m not positive.
FYI, I’ve forwarded your comments to the product design team for Reporting Services. I can’t guarantee that the issues will get fixed, but I can guarantee that your comments will be reviewed and the issues will be investigated.
Naw, this was just a rant so I could blow off some steam. Not looking for a lot of responses, really, perhaps from some others who’ve had problems with this thing (or perhaps it’s just me.)
Yeah, it’s one of MS’s new (?) software development tools that I’m bitching about - Reporting Services for Visual Basic .NET. There’s not much about it on the web, the online “manual” barely deserves the name, and it’s just damned frustrating, especially as I’ve spent the past five-odd years doing stuff in MS Access (which has its own report designer, and enables you to do all the things I’m bitching about in my third post. Including crash. )
My biggest problem is I’m not a programmer - I’m an operations guy who knows a lot of Access, and was asked to help design reports as the company converts from Access to SQL (5 years ago the company had 24 FT employees, today it has 125). I took a few minutes to look at RS, saw that it was “really like” Access, blithely said “No prob!”, and here I am today. :smack:
Yeah, they’re used to it–it’s not like they never read anything posted on the Internet, after all. But anyway, I did omit the part about the goats. Left in some of the other profanity, though.
Yeah, but bear in mind that since it takes Microsoft three tries to get a product right, you’ll have to settle for something like “overly affectionate marmots” till around SP2.
People use Avery labels. Avery Labels, have, in fact, evolved to be the leading standard here in the US. Avery Labels, in fact, are so standard that every product, from Publisher to Excel, from Word to Access to Works, that MS writes that is capable of printing data has either Avery Label templates or Avery Label wizards.
