Got more questions? Find advice on: SQL | XML | Regular Expressions | Windows
in Search
Welcome to AspAdvice Sign in | Join | Help

Crystal .NET Blog

Sample codes, tips, random rantings on Crystal Reports, Crystal Enterprise etc...

custom ADO.Net datasets

Q:

I want to use the “push mode“ with custom ADO.Net datasets passed to the report engine.

What is the best method to get the data ? Stored procedures or views ?

How can I get the fields definition at design time, without creating typed datasets?

 

A:

In theory, there is no difference if you get your data from stored procedure or views. It is entirely up to you what is best for your application. It is faster for us to use View and Stored Proc directly instead of data set.

You can design the report by connecting to a database with analogous data schema, and not use strongly-typed dataset. Then push in the dataset at runtime.

The report engine has the Database member will show users the field definitions.

 

Gook luck.

Sponsor
Published Thursday, September 09, 2004 10:37 AM by crystal

Comments

 

crystal said:

Thanks for your reply.

The datasets that will be "pushed" to the report don't follow the exact structure of the database tables, since are created from joins between multiple tables.

I like to use datasets and the "push model", instead of views or sps, since I like to have full control over the data.

What about "field definition" files. Are worth to look more into it? How can I create them? (I'm using the .NET version of Crystal Reports).

Thanks,
Stefanos
September 9, 2004 1:14 PM
 

crystal said:

In the brief but eloquent words from our architect:

"It was the old technology (Field Definition). Don't use it."

thanks,
Y
September 9, 2004 1:27 PM
 

crystal said:

Well, if you must create a report without using strongly typed DataSets or a database, then here is a doc on how to create *.ttx files for use with crdb_fielddef.dll:

http://support.businessobjects.com/communityCS/TechnicalPapers/scr8_ttxado.pdf.asp
September 24, 2004 2:32 AM
Anonymous comments are disabled