THis should be simple..!!! .DLL's and stuff!!

[jhowley58]

Hi,

I developed an Access 2000 database system on a Windows 2000 server and distributed it to various W2K Pro, Win 98 clients. It wouldn't compile on any of the clients.. After stumbling around for a while I realised that RunTime libraries were involved and that the clients had older Run Time libs..

If I develop an Access 2000 system on Computer 'A' and distribute it to Computers B,c,d,f etc, do all those Pcs have to have the same versions of referenced dlls like msadox.dll?

If so, can I just copy the relevant .dll to the same 'pathed' folder in all the target computers and count on the compilation working?


JohnH

 

[ctarr]

You'll probably want to ask this in the Microsoft:Access or related forums (better answers).

To answer your question, yes and no. You've got to be very careful about replacing DLL's. You can really screw systems up and break other apps by updating some DLL's.

You may want to change your 2000 version by selecting the option to downgrade (if this is available it may be new to Access 2002). Tools, database utilities (near compact and repair menus).

Otherwise, you'll have to redevelop the VBA by referencing other DLL's. For ex. Instead of using ADO you will need to go down to DAO.

I had a similar problem with the simple (built-in function)replace(). It was never developed in 97 it was new to 2000. I had to write my own replace function and use it on my 97 machines. Uh, what a mess.

 

[jhowley58]

Thanks - will do.. ( not the downgrade - the ask on other list ))

JohnH..