views:

39

answers:

4

Good morning fellow stack overflow people, I have a question that sounds like the start of something from the daily wtf.

The company that I work for is not so much sacred of new technology they just seem to let things slip, you know the type, “It worked 5/6+ years ago so I don’t see why we should change it”

Despite this I have managed by hook or by crook to get an installation of SQL server 2008R2 to develop on which has the reporting services. Excellent I think, I can finally start moving some of the access applications to VB.net and use SSRS to provide some embedded reports, everyone is happy.

But not so fast, it turns out the standard build of desktop here only has .net1.1. I have managed to dust off a copy of visual studio 2003 (The last edition that could target 1.1) and built a few little tests to check DB connectivity. The problem I am having is the report viewer control is only available in .net2.0 and above.

So what options do I have for displaying my SSRS reports in a VB.net1.1 thick client application?

Before anyone asks the following options are out

  • Going anything web based (Farrrrrrrrrr too modern for the company + no web server)

  • Upgrading to a version of .net released after George Bush the 2nd lost an election but still became president

  • Changing jobs

Sorry for the long question but I thought some background would help

A: 

I would go for a browser control but I think they only started including that in 2.0. But I think you can still do something like that in 1.1 (it has been to long to be sure).

I think if you install SSRS on the sqlserver you could turn on IIS on that server and then use that to make your reports and show them in the browser control.

SSRS (I'm pretty sure it came out somewhere around 2005) is not old enough to have many other options.

chrissie1
Topic starter wrote that he has no options of "Going anything web based". SSRS was available for SQL Server 2000 as add-in. But it is irrelevant to question
vgv8
Thank you for your answer, maybe I should have cleared a few points up. At the moment to test the reports I have setup a reporting server on the same box and just give out the URL to that specific report and they do everything though IE(Version 6 naturally) on their computer.I really would like to keep everything thick client and not have a browser control that points to a report if it can be avoided
Kevin Ross
A: 

If you work with VB.NET 1.1 all the time then it is strange question. How did you program in it before?

Use any available dataview control (I already do not remember - DataGrid, DataList, Repeater) from .NET1.1. There is nothing in ReportViewer that could not be done before its appearance, in .NET1.1.
What is the problem?


Update:
I remember seeing code projects reproducing ReportViewer in .NET1.1 few years ago though I cannot find it now. Anyway, it seems to me the problem of just reading .NET1.1 docs and searching internet.

vgv8
I don’t recall saying I work with VB.net 1.1 all the time, it’s a newish field to me and this is the first time I have tried to do anything that involves displaying reports. I am aware of how to use DataGrid and other controls to display data, I’m after a way to display the rich reports built using Report Builder 3.0. As I said if we had the 2.0 framework then no problem but we don’t
Kevin Ross
A: 

Sorry if this is a blunt statement but sometimes, you've got to bite the bullet and do the right thin.

If you really want to use reports and you've found the minimum version of the .NET framework is 2.0 then go ahead, find an internet connection somewhere and upgrade the computers.

If you can't do that, forget about it and go back to your VB6 or whatever you're using. Besides, .NET Framework 2.0 sp1 is less than 30MB. If you can't find a decent internet connection (either at your workplace or somewhere else) to download it then you might as well abandon it.

And I'll add as well. VS2003 IS OLD! Get yourself minimum VS2005, even if it's Express edition, it's good enough and stop whining.

Alex Essilfie
I wish I could just take it upon myself to upgrade all the computers to a more modern version of the .net framework but I cant, the decision is out of my hands and is not up for debate. I am fully aware of how old VS2003 is hence in my OP I said I had to “Dust a copy off”. I’m actually running VS2010 for doing some CLR stuff but that can’t target the 1.1 framework. I know it’s a bad situation but that’s that one I find myself in, I had already put forward the upgrade option but it was knocked back hence why I ruled it out in my OP
Kevin Ross
A: 

Someone had the same question back in Feb. Maybe this might send you down the right path:

http://stackoverflow.com/questions/566133/using-ssrs-in-asp-net-1-1

D.S.