Missing: Microsoft ADO Ext. 2.x for DDL and Security

[Anth Stever]

I created an DB with Acess 2002 (2000 format for the MDB's) and kept the
tables separate from the app... Used code from the Developer's Handbook
(Getz/Litwin) to automatically relink the tables. Works fine on 2002
systems but some folks with 2000 are unable to get the reference to
"Microsoft ADO Ext. 2.x for DDL and Security" functional. It shows up as
"Missing" when they check it in the list. Does that mean that MSADOX.DLL is
not on the system?

1) How do I get them up and running?
2) Is that file part of the Office Service Release 1/1a)?
3) What's the best way to distribute this as a working app for both Access
2000 and 2002?

Thanks!

 

[Douglas J. Steele]

It doesn't necessarily mean that they don't have it: you'll get that same
message if they've got a different version than you (or, sometimes, if it's
in a different location).

No, it doesn't come from the Office Service Releases: it's part of MDAC
(which you can get to from http://www.microsoft.com/data)

If you can't get everyone onto the same version of MDAC, you may be forced
to change your code to use Late Binding, so that you don't have to set a
reference. Tony Toews has some details about this at
http://www.granite.ab.ca/access/latebinding.htm

 

[Anth Stever]

Thanks, Doug

How can I check to see what version of MDAC I've got? Is the version number
of Microsoft ADO Ext. 2.x for DDL and Security the indicator?

/\nth

 

[Anth Stever]

Just to be a tad more explicit, the version of MSADOX.DLL I have is
2.71.9030...

 

[Douglas J. Steele]

You probably have MDAC 2.7, but I'd advise using the Component Checker to be
sure.

Check out http://support.microsoft.com/default.aspx?kbid=301202&product=mdac

 

[Anth Stever]

Thanks, Doug. The other question that no one answered was:

"What's the best way to distribute this as a working app for both Access
2000 and 2002?"

 

[Douglas J. Steele]

Why not just distribute it in Access 2000 format? Access 2002 is fine with
that format: in fact, out of the box, Access 2002 uses Access 2000 format
(you have to tell it to use Access 2002 format)

 

[Anth Stever]

Sorry, I wasn't clear enough in the problem statement... I meant to say
that I wanted to not have to deal with users having to worry about which
MDAC they have and so forth. I guess the answer I was looking for was
something like: "You really need the Developer Edition so you can turn it
into an .exe with an install routine that sets up the users' systems."

Regards,

/\nth

 

[Douglas J. Steele]

But that wouldn't necessarily guarantee it, since if, for example, they had
a new version of MDAC installed, your installation wouldn't (or at least
shouldn't) replace it.

(And the Developer Edition doesn't turn Access applications into
executables: all it does is package your application together with a
royalty-free run-time version of Access. it doesn't change your application
in any way, shape or form)

What does your code look like? Have you tried using Late Binding, rather
than setting a reference to ADOX?

 

[Anth Stever]

Bummer. The other bummer is that I don't know what "Late Binding" is...
I'll do some research...

Doug, thank you!

 

[Douglas J. Steele]

Start by seeing what Tony Toews has at
http://www.granite.ab.ca/access/latebinding.htm