Bonnie

Confused a little, I'm a beginner in .Net.

Basically (and I should've explained in the first post :)), I want to create a Crystal Report based on some Datasets that are created in the app at runtime, but I can only create fields in the report at design-time using Connections and Datasets created in the project.

Does that make sense?

Thanks
Kev

>Kev,
>
>Ah ... that's a longer answer! <g> I use Typed DataSets, so that further complicates things.
>
>Actually, I use a tool that we wrote (in .NET) that creates a DataSet from a Stored Procedure. This DataSet is then used as the starting point for generating a Typed DataSet and a further sub-class of that (using another tool, written in VFP). Probably more information than you wanted to know. <g>
>
>If you have a lot of DataSets to create, and you're basing them on SQL SP's, then you can easily write the tool to do that too ... after filling a DataSet from your DataAdapter, simply use the ds.WriteXMLSchema() method to write an .xsd file. Then use that in your project. I hope I haven't confused you.
>
>~~Bonnie
>
>>Sort of, I think.
>>
>>What I meant was do you create your data-objects in code, or right-click on the project and select Add New Item, then select DataSet etc.etc.
>>
>>Kev
>>
>>>Kev,
>>>
>>>Not 100% sure what you're asking, but I'll take a stab at it. All our Data Objects are in their own separate projects. Connections and that sort of thing are stored in a DataAccess project. The DataSets are passed around between tiers. In a UI form I just add a reference to a Data Object and then assign variables. I'm not sure if that's what you're asking about or not ...
>>>
>>>~~Bonnie
>>>
>>>
>>>>Hi
>>>>
>>>>Does anyone add items to the project, or hard-code them?
>>>>
>>>>I've been creating classes and storing connections and datasets etc. into member variables, is that correct? Or should they be added to the project?
>>>>
>>>>Thanks
>>>>Kev