exposing datasets

[Guest]

Hey all,

I'm trying to wrap my dataset in a single business object and I'm wondering
the best way to expose it or if I should expose it at all.

If it's ok to expose it should I use:
public ds as dataset,
or
public property ds as dataset
or
welcome other suggestions here.

If you say it may not be a good idea in some cases my dilemma would be: I
have 2 forms I can use a public function to return a dataset on the first
form1 but what if I wanted to use that same dataset on another form say form2
how do I get to the dataset if it's not publicly available.

Thanks in advance,
rodchar

 

[Ken Tucker [MVP]]

Hi,

A property is better. You have the ability to make the property
validate any changes made or to make the data readonly if necessary.

Ken
--------------------
Hey all,

I'm trying to wrap my dataset in a single business object and I'm wondering
the best way to expose it or if I should expose it at all.

If it's ok to expose it should I use:
public ds as dataset,
or
public property ds as dataset
or
welcome other suggestions here.

If you say it may not be a good idea in some cases my dilemma would be: I
have 2 forms I can use a public function to return a dataset on the first
form1 but what if I wanted to use that same dataset on another form say
form2
how do I get to the dataset if it's not publicly available.

Thanks in advance,
rodchar

 

[Guest]

Awesome.Thank you.
Is that considered violating encapsulation though?