Re: Using ADO and DAO in same mdb

On Jul 29, 10:38 am, Barry Edmund Wright
<bwright_msacc...@xxxxxxxxxxxx> wrote:
hi,

I started a project with a company who hired two Access developers
because of the tight timeline. Problem, I use DAO the other developer
uses ADO. I believe we can use both ADO and DAO by putting the DAO
reference first and then the ADO if he fully qualifies all the ADO
declarations. Is this correct?

I'm so happy you said that any comments (would be) appreciated. Here
are mine:

Two developers each using a different technology is going to save
time?

What version of Access is going to be used? Does the ADO developer
bind forms in an MDB to an ADO recordset? Is this fast and simple? How
about reports? Maybe the project will use unbound forms. Oh goodie,
that's another way to speed up development, right? Maybe it will use
unbound reports too? Yes, I've used a few. Oh wait, that was in an
ADP. Regardless, who else has? Hands up! Please, send me a couple as
text objects and I'll publish them for all to see. (Yes, Terry I know
you probably have done this, but I'm being sceptical only of mortals
tonight.)

There are lots of Access developers who know DAO but don't know ADO.
But there's one who knows ADO but not DAO? Did he/she learn on ADPs?
If so then what level of MDB expertise does this person have? Even the
world's greatest fan of ADO (that's me) would use DAO in the situation
you're describing. He/she can't handle both DAO and ADO? You're
kidding! You're working with the mentally handicapped?

Who's going to maintain this monstrosity? It would have to be somebody
whose so unskilled he/she can't get any other work. Surely no on else
would touch it!

This whole idea is just idiocy. The person who hired the two
developers should be fired. And the DAO developer must be starving or
he/she would never get involved in this barrel of alligators. The ADO
developer is probably just really stupid or completely inexperienced.

.

Relevant Pages