Re: Using ADO and DAO in same mdb
- From: SmartbizAustralia <tom@xxxxxxxxxxxxxxx>
- Date: Tue, 31 Jul 2007 04:57:30 -0700
I like the response above.
There is no need to be worried about using dao and ado at the same
time.
You have to use dao to refresh the linked tables?
One can argue that ado is better, but dao seems to take less lines and
is simpler!
Sometimes you need ado to link to say dbII and SQL whilst most of the
time dao will be okay.
Having two developers is not an issue if they communicate okay plus
use similiar naming conventions.
One note though is be careful of binding forms with code if you can
just use linked tables!
You might as well use asp.net if you don't want to take advantage of
access's data binding.
I've seen nightmare coding with unbound forms when this wasn't
necessary.
Regards,
Tom Bizannes
Microsoft Access Development
Sydney, Australia
http://www.smartbiz.com.au
.
- References:
- Using ADO and DAO in same mdb
- From: Barry Edmund Wright
- Re: Using ADO and DAO in same mdb
- From: rkc
- Using ADO and DAO in same mdb
- Prev by Date: Re: 2007 Access
- Next by Date: Re: Access Jet-Engine versus MSDE / SQL
- Previous by thread: Re: Using ADO and DAO in same mdb
- Next by thread: Re: Using ADO and DAO in same mdb
- Index(es):
Relevant Pages
|
