I am not sure exactly where this su

[etrain]

I am not sure exactly where this subject falls so if you see this posted in multiple areas I apologize.

I am deploying an Access2k application. It has DLL references to ADO 2.5 Library and ADO Ext 2.5 for DDL and Security among others. When I deploy it to some people it works find no problem but to this one persons computer these 2 come up missing and they get a runtime error. I can manually go in and remove the missing and re-reference them but it is version 2.1 not 2.5. I copied the DLL files from my machine and placed them on this persons machine thinking that would solve the problem but it doesn't. The DLLs are still missing and when I manually reference them it is still version 2.1. Whether 2.1 or 2.5 is not the problem just the fact that the application shows them missing.

I have read through many threads concerning linking references via code etc but nothing seems to solve my problem. Anyone have a way to solve it? I thought by reloading Office 2k on their machine would solve the problem but that doesn't work. Why would the same file on my machine disply version 2.5 but when I copy the same to their machine it shows 2.1.

I am for the most part unfamiliar with DLLs and such so this could be why my confision.

thanks
etrain Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain

 

[etrain]

%-)Sorry about the subject everyone. I hit submit when I meant to hit preview. I would change it but can not find a way to do that. The subject should have been "Missing DLL's and then older version DLL after manually referenced, when application deployed..." Remember the Past, Plan for the Future, yet Live in the Now for tomorrow may never come.
-etrain

 

[WildHare]

Why would the same file on my machine disply version 2.5 but when I copy the same to their machine it shows 2.1.

It wouldn't. You must be looking at two different files.

c:\windows
c:\windows\system
c:\windows\system32
c:\program files\Micosoft office\office
c:\program files\Microsoft office\office\1032
c:\program files\Common Files
c:\program files\Common Files\Shared
c:\program files\Common files\Microsoft

are just a few of the places where MS tends to spew it's DLL files during installation. Have you done a search on the file name itself and seen if there may be >1 copies floating around?



Remember, you're unique - - just like everyone else
Another free Access forum:

http://www.forumco.com/jmhare

http://www.jmhare.com

 

[longhair]

Just an outside question... same OS? I have seen some versions of "windows" do some odd things.

Longhair