Posted by Jim Carlock on 10/02/07 23:15

"Steve" wrote...
: btw, you don't need to use DAO.OpenDatabase unless you have
: another class with the same interface...which is 'collision'.
: even though you specify DAO.OpenDatabase and avoid the
: collision, it only resembles namespaces here because you are
: trying to acheive the same thing as a namespace. however, i
: have to keep saying, they are NOT the same.
:
: make sense?

Right. I knew that I did not need DAO.<object> or DAO.<method>
but it makes the code more readable, especially since ADODB uses
alot of the same objects and methods. DAO works great with alot
of things... a heck of a lot better than ADODB (when working with
MicroSoft Access, Excel, et al). I learned to use DAO and it I if
it works for me I see no reason to use anything else. <shrug>

ADODB left a really really bad taste in my mouth at one time. I
don't want to go into that. That was a mess.

If I can only figure out how to get PHP to link/connect to an
ActiveX DLL without use any of that CreateObject syntax...

--
Jim Carlock
Swimming Pool, Spa And Water Feature Builders
http://www.aquaticcreationsnc.com/

[Back to original message]