Showing posts with label regarding. Show all posts
Showing posts with label regarding. Show all posts

Wednesday, March 28, 2012

Report Design help for Newb - Regarding Date Paramaters

I have been trying very hard for days now to build a report using VS 2003.net
I just need to query an order table by a date range. ie) from date a to
date b. The order table contains PO's and have recorded dates. I just need
an example of how to report based upon date range. Seems simple enough,
just cant figure it out.I assume you mean you want the user to be able to specify the date range?
If you currently have a sql statement that returns all orders and have a
report that displays that data, simply modify the sql statement and specify:
where datefield between @.startdate and @.enddate
That will automatically create report parameters. When you preview the
report, it will prompt you to type in start and end dates.
For more info, just do searches for query parameters and report parameters.
Mike G.
"tdodd" <tdodd@.discussions.microsoft.com> wrote in message
news:6A7F2EE5-FAFA-4852-B771-35FBC9431D71@.microsoft.com...
>I have been trying very hard for days now to build a report using VS
>2003.net
> I just need to query an order table by a date range. ie) from date a to
> date b. The order table contains PO's and have recorded dates. I just
> need
> an example of how to report based upon date range. Seems simple enough,
> just cant figure it out.

Tuesday, March 20, 2012

Report Builder Fails to Launch

Good day:

I've searched and found a whole lot of information regarding Report Builder's occasional failures to launch, but every single suggestion has not worked for me. I'll try to describe this as completely as possible.

PC 1: Login with my user id, navigate to either my test or production report server, click 'Report Builder'; application launches and can be used as expected. Login with a 2nd user id, and it works. OS is Win2003 Server. Because both logins work on this PC, which tells me the security credentials are set correctly.

PC2: Login with my user id, navigate to either my test or production report server, click 'Report Builder'; application fails to launch. I do not receive an error message or dialog. The 'frames' for the Report Builder form flash momentarily on the screen. Login with same 2nd user id, and it fails the same way. OS is WinXP SP2; all updates.

PC3: Login with my user id, navigate to either my test or production report server, click 'Report Builder'; application fails to launch. I do not receive an error message or dialog. The 'frames' for the Report Builder form flash momentarily on the screen. Login with same 2nd user id, and it fails the same way. OS is WinXP SP2; all updates.

On PC2 and PC3, I navigate to the ClickOnce cache in my profile, right-click and 'run as' the reportbuilder.exe file. Choosing 'run as' my login and providing a password -- voila -- the application runs. I have to manually set the link to the report server, but it appears all else works fine. Same situation when I use my 2nd user id. If I don't 'run as' and provide the password (just double-click to launch the file), I get the same 'flash frames' above.

Ultimately, the push is to get PC2 and PC3 to function as does PC1. My resident .NET expert is stumped, as am I. Please help.

I must not have provided enough information. What do I need to post in order to explain this situation better?

|||

The troubleshooting has begun.

WinXP SP2 w/o all the updates or .NET. Click 'Report Builder', which errors that I don't have .NET 2.0. Download and install redistributable package -- voila -- report builder works. Note there is nothing else on the box except WinXP SP2 and .NET 2.0.

This leads me to conclude that there's something in one of the patches from MIcrosoft that is preventing the report builder from working. PC2 ( from my original post ) has all the latest patches as well as a bunch of applications. PC3 has all the latest patches with SQL Server 2000 SP4 and Office 2007. Neither PC2 nor PC3 can run Report Builder. I'm now on PC4.

It's either a patch from microsoft causing this issue, or the order in which the patches were applied. I'm going to be testing the Report Builder after every installed patch ( yes -- I am that interested in getting to the bottom of this that I'd download over 75 patches one at a time ).

If I find anything, I'll post again.

|||

So apparently the software for a Kensington Trackball will prevent a .NET 2.0 ClickOnce application from launching. Like Report Builder. No kidding. I've uninstalled the tracball software and Report Builder works. Reinstalled the tracball software, Report Builder fails to launch. Uninstall the tracball software (leaving it off this time) Report Builder works.

Nice.