Reference DAO 3.6 Object Library or DAO 2.5/3.51 Compatibility Library
Quote:
>Hi,
>Windows 98 SE
>Visual Basic 6.00 (SP4)
>Access 97 installed - if relevant
>I have an application that is heavily dependent on a database. The
>application has travelled through VB3 pro, VB4 pro and now VB6 (SP4).
>At the VB4 stage I referenced the DAO 2.5/3.50 Compatibility Library
>and in VB6 I reference the DAO 2.5/3.51 Compatibility Library.
>Is there any reason why I can't reference the DAO 3.6 Object Library,
>if not, are there any potential pitfalls to look out for. Do I have to
>do anything with the existing database structure to accommodate the
>change?
Ah.
We had *big* problems, but unfortunately I did a rush debug on
site without any tools or, idiot I must have been that day, proper
logging.
We upgraded from VB5 to VB6 and took our applications to DAO
3.60. Suddenly some client machines couldn't read data at all; my
first guess was that machines with Access 2000 installed were working
but those with Access 97 were broken, but that didn't match up with
what was happening *if I'm remembering correctly*. As it was we
needing things working immediately: I headed back to the office,
rolled back to 3.51, recompiled, reinstalled on the client machines
and everything worked fine again, on all machines.
Frustratingly enough, some of the broken machines didn't even have
an existing DAO installed -- no Access, no shared path in the
filesystem. I'd have to check, but I think I've even gone so far as
to install the DAO in the application's directory. (erk.)
Incidentally, there seem to be multiple builds of 3.60 out there.
We're staying away until we see 3.61.
Summary: it's a change. Expect something to break. Watch
everything very very closely until you're *sure* it's working, and
if your application works in-house, don't expect it to work anywhere
else until you've proved it.
Yuck.
Anyway, hoping your upgrade goes smoother than ours...
Cheers, butting
