-
Coming from ReportBuilder...
(warning: possibly stupid questions may follow)
I've currently in the process of porting a project written in Delphi with
reports generated in ReportBuilder 10.
I've never had anything to do with creating reports in a .NET environment
previously so I'm just wondering if there are any things I should be aware
of? The new application will be running off an SQL server 2005, but I would
also like it to be able to run off SQL server express.. Is this feasible?
I'm also wondering about the architecture.. Do the reports *have* to be
generated server side and be fetched via WS or can I embed reports in my
application and just fetch the data from the sql-server? If both methods are
doable, what's the best approach? The application will primarily be used
in-house with a small load but may be turned into a commercial project
somewhere down the road.
Any help is much appreciated!
Håvard
-
Re: Coming from ReportBuilder...
Which front-side client language will you be using? Delphi Win32, Delphi
..NET, C#, VB.NET?
Alain Quesnel
alainsansspam@logiquel.com
www.logiquel.com
"Håvard Olerud Eriksne" wrote in message
news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
> (warning: possibly stupid questions may follow)
> I've currently in the process of porting a project written in Delphi with
> reports generated in ReportBuilder 10.
> I've never had anything to do with creating reports in a .NET environment
> previously so I'm just wondering if there are any things I should be aware
> of? The new application will be running off an SQL server 2005, but I
> would also like it to be able to run off SQL server express.. Is this
> feasible? I'm also wondering about the architecture.. Do the reports
> *have* to be generated server side and be fetched via WS or can I embed
> reports in my application and just fetch the data from the sql-server? If
> both methods are doable, what's the best approach? The application will
> primarily be used in-house with a small load but may be turned into a
> commercial project somewhere down the road.
>
> Any help is much appreciated!
>
> Håvard
-
Re: Coming from ReportBuilder...
On Mar 3, 4:14*pm, "Alain Quesnel" wrote:
> Which front-side client language will you be using? Delphi Win32, Delphi
> .NET, C#, VB.NET?
I'm writing the application using C# in VS2008
-
Re: Coming from ReportBuilder...
In that case, you can use the .NET Report Control for either C# web apps or
C# windows apps. Personally, I prefer using the web based report server.
Then your reports are served via a web browser, which means zero deployment.
All you need on the client side is MSIE 6 or 7. End-users can even write
their own ad-hoc reports via a web browser with Report Builder (comes out of
the box with MSSQL/SSRS 2005).
Alain Quesnel
alainsansspam@logiquel.com
www.logiquel.com
"Håvard Olerud Eriksne" wrote in message
news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
> (warning: possibly stupid questions may follow)
> I've currently in the process of porting a project written in Delphi with
> reports generated in ReportBuilder 10.
> I've never had anything to do with creating reports in a .NET environment
> previously so I'm just wondering if there are any things I should be aware
> of? The new application will be running off an SQL server 2005, but I
> would also like it to be able to run off SQL server express.. Is this
> feasible? I'm also wondering about the architecture.. Do the reports
> *have* to be generated server side and be fetched via WS or can I embed
> reports in my application and just fetch the data from the sql-server? If
> both methods are doable, what's the best approach? The application will
> primarily be used in-house with a small load but may be turned into a
> commercial project somewhere down the road.
>
> Any help is much appreciated!
>
> Håvard
-
Re: Coming from ReportBuilder...
"Alain Quesnel" wrote in message
news:urzJlGXfIHA.5620@TK2MSFTNGP04.phx.gbl...
> In that case, you can use the .NET Report Control for either C# web apps
> or C# windows apps. Personally, I prefer using the web based report
> server. Then your reports are served via a web browser, which means zero
> deployment. All you need on the client side is MSIE 6 or 7. End-users can
> even write their own ad-hoc reports via a web browser with Report Builder
> (comes out of the box with MSSQL/SSRS 2005).
OK, thanks. Since the application is based on WinForms I think I'll go with
the Report Control. Last question, is this similar(ish) to use as
ReportBuilder?
Cheers,
Håvard
>
>
>
> Alain Quesnel
> alainsansspam@logiquel.com
>
> www.logiquel.com
>
>
> "Håvard Olerud Eriksne" wrote in message
> news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
>> (warning: possibly stupid questions may follow)
>> I've currently in the process of porting a project written in Delphi with
>> reports generated in ReportBuilder 10.
>> I've never had anything to do with creating reports in a .NET environment
>> previously so I'm just wondering if there are any things I should be
>> aware of? The new application will be running off an SQL server 2005, but
>> I would also like it to be able to run off SQL server express.. Is this
>> feasible? I'm also wondering about the architecture.. Do the reports
>> *have* to be generated server side and be fetched via WS or can I embed
>> reports in my application and just fetch the data from the sql-server? If
>> both methods are doable, what's the best approach? The application will
>> primarily be used in-house with a small load but may be turned into a
>> commercial project somewhere down the road.
>>
>> Any help is much appreciated!
>>
>> Håvard
>
-
Re: Coming from ReportBuilder...
I think so, but I haven't worked with Reporting Services in that manner.
--
Alain Quesnel
alainsansspam@logiquel.com
www.logiquel.com
"Håvard Olerud Eriksen" wrote in message
news:uPStckXfIHA.4696@TK2MSFTNGP05.phx.gbl...
>
> "Alain Quesnel" wrote in message
> news:urzJlGXfIHA.5620@TK2MSFTNGP04.phx.gbl...
>> In that case, you can use the .NET Report Control for either C# web apps
>> or C# windows apps. Personally, I prefer using the web based report
>> server. Then your reports are served via a web browser, which means zero
>> deployment. All you need on the client side is MSIE 6 or 7. End-users can
>> even write their own ad-hoc reports via a web browser with Report Builder
>> (comes out of the box with MSSQL/SSRS 2005).
> OK, thanks. Since the application is based on WinForms I think I'll go
> with the Report Control. Last question, is this similar(ish) to use as
> ReportBuilder?
>
> Cheers,
> Håvard
>
>>
>>
>>
>> Alain Quesnel
>> alainsansspam@logiquel.com
>>
>> www.logiquel.com
>>
>>
>> "Håvard Olerud Eriksne" wrote in message
>> news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
>>> (warning: possibly stupid questions may follow)
>>> I've currently in the process of porting a project written in Delphi
>>> with reports generated in ReportBuilder 10.
>>> I've never had anything to do with creating reports in a .NET
>>> environment previously so I'm just wondering if there are any things I
>>> should be aware of? The new application will be running off an SQL
>>> server 2005, but I would also like it to be able to run off SQL server
>>> express.. Is this feasible? I'm also wondering about the architecture..
>>> Do the reports *have* to be generated server side and be fetched via WS
>>> or can I embed reports in my application and just fetch the data from
>>> the sql-server? If both methods are doable, what's the best approach?
>>> The application will primarily be used in-house with a small load but
>>> may be turned into a commercial project somewhere down the road.
>>>
>>> Any help is much appreciated!
>>>
>>> Håvard
>>
>
-
Re: Coming from ReportBuilder...
I think so, but I haven't worked with Reporting Services in that manner.
--
Alain Quesnel
alainsansspam@logiquel.com
www.logiquel.com
"Håvard Olerud Eriksen" wrote in message
news:uPStckXfIHA.4696@TK2MSFTNGP05.phx.gbl...
>
> "Alain Quesnel" wrote in message
> news:urzJlGXfIHA.5620@TK2MSFTNGP04.phx.gbl...
>> In that case, you can use the .NET Report Control for either C# web apps
>> or C# windows apps. Personally, I prefer using the web based report
>> server. Then your reports are served via a web browser, which means zero
>> deployment. All you need on the client side is MSIE 6 or 7. End-users can
>> even write their own ad-hoc reports via a web browser with Report Builder
>> (comes out of the box with MSSQL/SSRS 2005).
> OK, thanks. Since the application is based on WinForms I think I'll go
> with the Report Control. Last question, is this similar(ish) to use as
> ReportBuilder?
>
> Cheers,
> Håvard
>
>>
>>
>>
>> Alain Quesnel
>> alainsansspam@logiquel.com
>>
>> www.logiquel.com
>>
>>
>> "Håvard Olerud Eriksne" wrote in message
>> news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
>>> (warning: possibly stupid questions may follow)
>>> I've currently in the process of porting a project written in Delphi
>>> with reports generated in ReportBuilder 10.
>>> I've never had anything to do with creating reports in a .NET
>>> environment previously so I'm just wondering if there are any things I
>>> should be aware of? The new application will be running off an SQL
>>> server 2005, but I would also like it to be able to run off SQL server
>>> express.. Is this feasible? I'm also wondering about the architecture..
>>> Do the reports *have* to be generated server side and be fetched via WS
>>> or can I embed reports in my application and just fetch the data from
>>> the sql-server? If both methods are doable, what's the best approach?
>>> The application will primarily be used in-house with a small load but
>>> may be turned into a commercial project somewhere down the road.
>>>
>>> Any help is much appreciated!
>>>
>>> Håvard
>>
>
-
Re: Coming from ReportBuilder...
"Alain Quesnel" wrote in message
news:OseId8hfIHA.5624@TK2MSFTNGP02.phx.gbl...
>I think so, but I haven't worked with Reporting Services in that manner.
OK, thanks. I've started looking into the issues now and it looks promising
:)
Håvard
>
> --
>
> Alain Quesnel
> alainsansspam@logiquel.com
>
> www.logiquel.com
>
>
> "Håvard Olerud Eriksen" wrote in message
> news:uPStckXfIHA.4696@TK2MSFTNGP05.phx.gbl...
>>
>> "Alain Quesnel" wrote in message
>> news:urzJlGXfIHA.5620@TK2MSFTNGP04.phx.gbl...
>>> In that case, you can use the .NET Report Control for either C# web apps
>>> or C# windows apps. Personally, I prefer using the web based report
>>> server. Then your reports are served via a web browser, which means zero
>>> deployment. All you need on the client side is MSIE 6 or 7. End-users
>>> can
>>> even write their own ad-hoc reports via a web browser with Report
>>> Builder
>>> (comes out of the box with MSSQL/SSRS 2005).
>> OK, thanks. Since the application is based on WinForms I think I'll go
>> with the Report Control. Last question, is this similar(ish) to use as
>> ReportBuilder?
>>
>> Cheers,
>> Håvard
>>
>>>
>>>
>>>
>>> Alain Quesnel
>>> alainsansspam@logiquel.com
>>>
>>> www.logiquel.com
>>>
>>>
>>> "Håvard Olerud Eriksne" wrote in message
>>> news:ueB8gsTfIHA.2000@TK2MSFTNGP03.phx.gbl...
>>>> (warning: possibly stupid questions may follow)
>>>> I've currently in the process of porting a project written in Delphi
>>>> with reports generated in ReportBuilder 10.
>>>> I've never had anything to do with creating reports in a .NET
>>>> environment previously so I'm just wondering if there are any things I
>>>> should be aware of? The new application will be running off an SQL
>>>> server 2005, but I would also like it to be able to run off SQL server
>>>> express.. Is this feasible? I'm also wondering about the architecture..
>>>> Do the reports *have* to be generated server side and be fetched via WS
>>>> or can I embed reports in my application and just fetch the data from
>>>> the sql-server? If both methods are doable, what's the best approach?
>>>> The application will primarily be used in-house with a small load but
>>>> may be turned into a commercial project somewhere down the road.
>>>>
>>>> Any help is much appreciated!
>>>>
>>>> Håvard
>>>
>>
>
>
>