EXE & DLL : Best Approach??

I have a system which I am designing in the following format :

I have some Data Classes (which handle all my stored proc calls etc) which are used by multiple classes (which are each based on seperate tables) which are used by my forms.

All my previous apps have been in one exe, this is my first with seperate exe and dll's.

What I want to know is which is the best method to use (or is there a better way) :

* Pass data in the form of a DataReader/DataSet from the multiple classes to the forms.
* Pass data in the form of arrays (after populating them from the DataReader/DataSet's) from the mulitple classes to the forms.
* Hold the DataReader/DataSets in the multiple classes and reference them from the forms.
* Reference the controls to populate (on the forms) within the multiple classes, and populate them within the classes.

Well first off, parameters. Use parameters to pass around data.

You can also make a public dataset variable in a class Shared to use it in other places

It is nice to see that you are breaking in to the N-Tier arena!:cool:

Firstly, your dll file should contain your classes that handle the loading of data.

The datasets should then represent a collection of objects, each record within the dataset representing an object.
A collection object should wrap the dataset object. The collection object should be returned to the forms classes.

To access a record (object) in the collection, the collection should read out the record and wrap that record in an object of the correct type. Each property should manage the reading and writing to the field in the record.

If binding is what you are after, you can include it into the collection object and each individual object too. This will provide solid OO way of manipulation data.

The first time you do this, it may seem like a lot of work. When it comes time to add constraints and other validation to the application, you will see the benefit in wrapping the dataset.

Take a look at the .net design patterns. This shows how to solve many common problems.

Cander : I know I have to pass parameters around!! ;)

shunt : I'll take a look at the .net design patterns. They seem to show what I'm after.

Cheers

I have the perfect article for you. If you have the msdn april 2003 then use the following link:
ms-help://MS.MSDNQTR.2003FEB.1033/dnbda/html/BOAGag.htm

alternatively use the following online url:
http://msdn.microsoft.com/library/en...asp?frame=true

This article is exactly what you need to read. It is not technical. It provides you with an architectural view of how you should code your application.

Freaky :D

I printed out that article last night, and read the first half of it on the way to work this morning.

You're right, it seems to be exactly what I'm after, and the best thing about it is after reading the first half, I seem to be doing everything the right way at the moment.

The second half of it is probably what I need to read up about.

Cheers again

Glad to see this is helping you!:D