bind report viewer to a report source during runtime

Question

0.00/5 (No votes)

See more:

hello everyone
i have a C# program that enables the user to make tables with specific name for the infinite number of clients in one database. so assume that we have lots of tables in one database with different names. i want the user can print the data of each of those tables he wants through the crystal reports but i don`t know how to set the report source to the report viewer and how to design the page he wants to print.
when we go through the "using the report wizard" we just can make a report and save it and then we can print it through report viewer but i want the user make it every time he needs and with every table he wants.
hope i explain good enough !
please help me.

Posted 5-Aug-11 7:30am

Saeed Jafarian

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Mycroft Holmes · Accepted Answer · 2011-08-06T03:01:00

Saeed you have one rotten database design, I mean really bad and you are running up against the first of many problems you are going to find b/c of your lousy design.

Have the report expect a dataset/datatable and use dynamic sql to service the data base on a specific name parameter. So you bind your report to a stored procedure (even if you hard code the table name for design purposes) and change the procedure after the report is designed to get the data from the name table.