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

Your opinion: Using DataAccess Enterprise Application Blocks 2.0

P: n/a
va
I'd appreciate any feedback

Where some of the Enterprise Application Blocks are pretty powerful, with
all the cool binding controls and the simplicity of combined objectsource and
sqlsource , does the DataAccess Enterprise Application Blocks 2.0 still have
the same benefits?
Feb 22 '06 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I treat all the EAB the same. They are robust (tested) pieces of code that
solve a certain problem space. Really, if it does what you need it to do,
there's very little reason NOT to it them. Yes, some times there are
alternatives which are better (like Log4Net > logging EAB), but if the
logging EAB did what you needed, I'd say go for it.

Karl
--
http://www.openmymind.net/

"va" <id************@forgetit.com> wrote in message
news:C3**********************************@microsof t.com...
I'd appreciate any feedback

Where some of the Enterprise Application Blocks are pretty powerful, with
all the cool binding controls and the simplicity of combined objectsource
and
sqlsource , does the DataAccess Enterprise Application Blocks 2.0 still
have
the same benefits?

Feb 22 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.