>>>>Hopefully SSRS is easy as you think/suggest. Speaking about To-Do, I have too much on my list. I keep thinking more and more often that maybe time to grow to 1 employee <g>.
>>>>Thank you.
>>>
>>>There is a learning curve and you have decisions to make.
>>>
>>>You can use the built-in ReportViewer control (using RDLC report definitions) on ASPX pages which gives you most of the features of SSRS, or you can use SSRS as a standalone website (using RDL definitions) which gives you the added capabilities of allowing users (in groups defined by you) to create or modify their own reports as well as view reports created by you.
>>>
>>>Generally, walk before you run applies here - use the reportviewer to make canned reports first! Reports created for the reportviewer can be ported to SSRS (RDL) reports if you decide to go that route.
>>>
>>>>
>>
>>Thank you for outlining the options and choices. Let me describe to you the first report I need to create and ask you to suggest the easier approach/path.
>>
>>One of the pages of the asp.net application is where user enters an order. On Submit a record is added to one of the tables. I also need to add the following feature to the Submit. A form (one-page report) with data from the newly created record in the table has to be printed (to a certain printer specified in the configuration). So this one-page report/form has to be "silently" printed and does not need to be modified by anybody but (maybe in the future by me). Which approach of the listed by you above would you recommend to follow?
>
>Use a reportviewer control. You can specify the output type.
>
>I'm not sure how you would accomplish printing directly to a printer w/o user interaction. That may not be easy (never tried it).

I was hoping that in Asp.net there would be a command similar to VFP (report form .. printer). I will have to search on this topic. Thank you for the suggestion to use the reportviewer.