April 12, 2010 at 6:13 pm
Thanks! You were typing at the same time as me.
That makes sense too. Maybe you're right. My biggest concern with the https to sql server was passing the credentials to ensure that every report/invoice was related to that specific Rep. But the Rep ID is the field that ties every table together.
I'll read some more on this possibility, see if I cant grasp it a little better.
April 13, 2010 at 3:16 am
TAMMYAUDETTE (4/12/2010)
Yes, this would be simply for downloading reports, invoices etc.But integrating the two? The two what? Sorry, I'm a little lost.
Given that this isnt a transactional or ecommerce project, I just want an online "client portal", where users can securely login to access a variety of their "client only" reports, would it be simpler to use a ASP.NET app to SQL Server?
I could call in some help if thats the best approach. I have a spending freeze on, when it comes to capital expenditures and such, but I have permission to bring in a temp programmer or devloper on a short term basis. This might be far out of my scope.
But if SSRS is still on the table, I'd liek to understand more.
I'm doing a project just like this one where I'm integrating asp.net with SSRS... You build the report with SSRS and then you use reportview control to present the data on the web (which helps you bypass the standard SSRS windows authentication security). You have the manually bind the data with each of the reports' datasources and then call the databind() method and bingo the report is shown outside your AD to anyone you wish to.
I have a portal where users login typing a login / password which is stored in the database. All my reports are based on that logon (which tells me their client #). From there all the reports are based on that id.
April 13, 2010 at 3:19 am
This might help you get started.
April 13, 2010 at 6:17 am
[/quote]
I'm doing a project just like this one where I'm integrating asp.net with SSRS... You build the report with SSRS and then you use reportview control to present the data on the web (which helps you bypass the standard SSRS windows authentication security). You have the manually bind the data with each of the reports' datasources and then call the databind() method and bingo the report is shown outside your AD to anyone you wish to.
I have a portal where users login typing a login / password which is stored in the database. All my reports are based on that logon (which tells me their client #). From there all the reports are based on that id.[/quote]
That sounds like exactly what I am hoping to achieve. I will take a look through the link you posted and see what I can find. Thanks!
April 13, 2010 at 8:58 am
Viewing 5 posts - 16 through 20 (of 20 total)
You must be logged in to reply to this topic. Login to reply