Re: DAO360.DLL - can I redistribute it?
From: StuartM (StuartM_at_discussions.microsoft.com)
Date: 02/01/05
- Previous message: Paul Overway: "Re: DAO360.DLL - can I redistribute it?"
- In reply to: Paul Overway: "Re: DAO360.DLL - can I redistribute it?"
- Next in thread: Brendan Reynolds: "Re: DAO360.DLL - can I redistribute it?"
- Reply: Brendan Reynolds: "Re: DAO360.DLL - can I redistribute it?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 1 Feb 2005 04:49:02 -0800
Thanks Paul,
We're looking at rewriting the application as multiple developers have just
bolted things on without any documentation of any kind or rationale (this was
before my time and not the way I would have done it!). It also needs to be
maintainable (without meaningless variables called "x", "y" or my favourite
"jj".... so we're using the opportunity to go for a rewrite - probably in
.Net. Your point about the only real advantage of ADO being its ability to
write common code for almost any database is definitely my prime reason for
moving to it. I'll probably still need to use DAO to reach the parts that
ADO/ADOX doesn't reach, but the aim will be to keep its usage to the bare
minimum.
We install the runtime of Access 2002 so I'll do a bit of checking to see
what version of Jet is installed by it and if it includes DAO 3.6.
My big worry about telling them to install MDAC is that when it installs the
various components it may have an impact on other programs on the target
machine. Call it paranoia, but I always aim to install the fewest components
that are necessary on a client's machine...
Cheers again,
StuartM
"Paul Overway" wrote:
> Older versions of MDAC include Jet 4.0...the newer ones do not. You can
> redistribute MDAC.
>
> Hate to disappoint you, but ADO will not necessarily be the answer to your
> problems. In fact, you may just wind up doing a lot of work for little or
> no benefit. If the database is Jet/DAO, you'll still need Jet on the target
> PC...whether or not you use ADO. The only real advantage to ADO is being
> able to write common code for nearly any database...i.e., when the SQL and
> schema used is common among the various database you might connect to. If
> the SQL for your application has syntax specific to a given database
> provider, ADO has little or no advantage. Jet SQL syntax in many cases is
> different than that used for other database providers, so...no advantage.
>
> --
> Paul Overway
> Logico Solutions
> http://www.logico-solutions.com
>
>
> "StuartM" <StuartM@discussions.microsoft.com> wrote in message
> news:3738DE35-6EC0-4FCB-AF87-C0E6364A3AD0@microsoft.com...
> > Hi,
> >
> > We've just had a problem with a customer not having DAO360.DLL installed
> > on
> > their machine (they were using NT4). Am I allowed to redistribute this
> > file?
> > I'm assuming it's part of MDAC, but I'd like to avoid telling the customer
> > that they need to download MDAC from Microsoft if I can.
> >
> > Many thanks,
> >
> > Stuart
> >
> > p.s. The sooner I can get this app converted to ADO the better :)
>
>
>
- Previous message: Paul Overway: "Re: DAO360.DLL - can I redistribute it?"
- In reply to: Paul Overway: "Re: DAO360.DLL - can I redistribute it?"
- Next in thread: Brendan Reynolds: "Re: DAO360.DLL - can I redistribute it?"
- Reply: Brendan Reynolds: "Re: DAO360.DLL - can I redistribute it?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|