Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Reporting Services / May 2005

Tip: Looking for answers? Try searching our database.

DataSet has no fields

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jon A - 28 May 2005 00:48 GMT
Please Help. I am calling a stored procedure which creates a SQL statement and
then  runs
exec (@SQL + @Where  + @Order)
Is there anyway to manual create fields. The Stored procedures returns the
same column names and number of columns?

Signature

Thanks,
Jon A

Mary Bray [SQL Server MVP] - 29 May 2005 22:35 GMT
Why don't you set the proc to just do a select of the fields you want until
the report is built, then change the proc back to the exec(string) command.
That way you'll have access to the fields in the builder.

> Please Help. I am calling a stored procedure which creates a SQL statement and
> then  runs
> exec (@SQL + @Where  + @Order)
> Is there anyway to manual create fields. The Stored procedures returns the
> same column names and number of columns?
Tim McOwan - 31 May 2005 11:01 GMT
Alternatively, you can go into the properties of the dataset that you want
fields for (by clicking the elipsis next to the name of the dataset on the
Data tab in report design) and go to the "Fields" tab. Here you can define
your fields manually and this will enable you to use them in your report
design. Be careful to name your fields exactly as they are returned from the
database otherwise RS will run into problems.

Also, another thing to try is to click on the "Refresh Fields" button on the
Data tab in report design. This executes the query and "figures out" what
fields are returned where it may not be immediately obvious from your query
design (especially where using Dynamic SQL is concerned).

Cheers
Signature

Tim McOwan

> Why don't you set the proc to just do a select of the fields you want until
> the report is built, then change the proc back to the exec(string) command.
[quoted text clipped - 5 lines]
> > Is there anyway to manual create fields. The Stored procedures returns the
> > same column names and number of columns?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.