'seems to be running Access 97' probably means that it is not
running Access 97 at all: it is probably using DAO to access
an A97 database.
Yes. That's what I was trying to get across even if I didn't know how
to say it. said:
Failure to initialise DAO may mean that DAO, VBA5, or Jet
are not installed correctly, or not registered (in the registry).
I have a dao360.dll file from my own purchased Access 2000
installation, and I'm sure I have quite a few of the "5" runtime files
(same thing as VBA5???) but don't know about the Jet stuff though came
across that in some attempts to fix. Nothing given re Jet, though,
but it was mentioned.
A more obscure cause may be the lack of an appropriate
licence key for Jet. Installing Access 97 normally installed
a licence key for Jet. In the absence of an Access/Jet licence
key, your code has to create a dbengine object before attempting
to create a recordset object. If this is not your code, there
would be not solution to that problem other than installing more
software (Office 97, Access 97, VBPro) until you found something
with a valid Jet licence key)
(david)
So even though one has Access 2000, that's why this wouldn't work? I
don't have Access 97.
I tried several fixes on the net, like getting dao350.dll. The
message would stop coming up, but then the program would crash. I
also then saw that, of course, I have dao360.dll. But this is an
older program and is using Access 97 mdbs.
I've always had problems with older mdb files, it seems. I've tried
before using a couple of dbs made in 97 in contracts and they wouldn't
work once/even when converted to Access 2000 so there seem to be
issues most of the time when converting.
Re the problem at hand, I'm only trialing it, so it seems like I won't
be buying it after all if I can't get it to work even as a trial <g>!
It's not a cheap program to begin with. <vbg>
Thanks.