Consider late binding. For example, instead of (early bound):

Dim oCat As ADOX.Catalog
Set oCat = New ADOX.Catalog

remove the reference to ADOX entirely and use (late bind):

Dim oCat As Object
Set oCat = CreatObject("ADOX.Catalog")

--

"Robin Hammond" wrote in message ...
Andy,

Your most reliable solution is probably to install MDAC 2.8 on each client
machine with your application if possible. It should include all the latest
data access libraries. As far as I know Office does not update these
consistently.

http://www.microsoft.com/downloads/d...DisplayLang=en

Robin Hammond
www.enhanceddatasystems.com


wrote in message
...
The above 2 libraries are used by my application, and they
appear in the references as follows:

Microsoft ADO ext. 2.7 for DDL and Security.
Microsoft ActiveX Data Objects Recordset 2.7 Library.

If I compile my application myself, it always initially
fails on my client's system, with the above showing as
MISSING. If I untick them, then go back in and look down
the list I find earlier versions of these libraries, which
work fine (but it's a real pain to have to do this). My
client is running Office XP just like me. It's as if
installing Office XP has not updated these libraries. Does
anyone know why? I use these libraries for another
application - an Acess one. Here I have the same problem -
different client.

Many thanks, Andy Keen