By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,234 Members | 1,908 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,234 IT Pros & Developers. It's quick & easy.

n-tier

P: n/a
hey all,

i have a simple logical n-tier solution and was wondering what the best
practice for something is.

i have a customer object in my business layer with shared data access
methods. in the retrieveACustomer routine, is it ok for me to instantiate my
customer object here and return it to the ui layer

public function retrieveCustomer as customer
dim ocust as new customer
.....
return ocust
end sub

what are some other ways to handle?

thanks,
rodchar
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
please help.

"rodchar" wrote:
hey all,

i have a simple logical n-tier solution and was wondering what the best
practice for something is.

i have a customer object in my business layer with shared data access
methods. in the retrieveACustomer routine, is it ok for me to instantiate my
customer object here and return it to the ui layer

public function retrieveCustomer as customer
dim ocust as new customer
....
return ocust
end sub

what are some other ways to handle?

thanks,
rodchar

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.