DllHell

[Guest]

I have an access application that uses a 3rd party OCX which is installed and
registerd in the windows/sytem32 folder.
Now the vendor has a new OCX with same name but is NOT binargy compatable. I
need to use it in the compile of my new application version.

Problem: when the new application installs and registers the OCX the old
version of the app fails

Customers want to install and try out new version of our app (buth then
thier old version is pooched) also they may install app anywhere but i'm
installing OCX in same windows/system32 folder.

Short of taking 3rd party vendor to woodshed for not making OCX binary
compatable else just renaming ocx what can I doo?

Thanks,
Sherwood

 

[John Vinson]

I have an access application that uses a 3rd party OCX which is installed and
registerd in the windows/sytem32 folder.
Now the vendor has a new OCX with same name but is NOT binargy compatable. I
need to use it in the compile of my new application version.

Problem: when the new application installs and registers the OCX the old
version of the app fails

Customers want to install and try out new version of our app (buth then
thier old version is pooched) also they may install app anywhere but i'm
installing OCX in same windows/system32 folder.

Short of taking 3rd party vendor to woodshed for not making OCX binary
compatable else just renaming ocx what can I doo?

Thanks,
Sherwood

It does not appear that this question has anything to do with
Microsoft Access databases (the subject of this newsgroup); I'd
suggest that you repost in a Windows newsgroup appropriate to your
version of Windows. The webpage can be confusing - scroll down the
list of subject areas and find an appropriate group for this question.

John W. Vinson[MVP]

 

[Douglas J. Steele]

Sorry, John, but I think it is appropriate:

"I have an access application that uses a 3rd party OCX which is installed
and registerd in the windows/sytem32 folder."

I was going to point Wiz to Peter Walker's site (as Peter had an interesting
twist on this), but I was unable to connect to it. Other than that, I don't
have an answer.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

 

[Van T. Dinh]

Peter's site was OK about a month ago but I can't access it at the moment,
either.

He is in New Zealand at the moment so I let him know as soon as he is back
in Sydney.

 

[Douglas J. Steele]

Thanks, Van. Just think of how much travel could have been saved if Peter
had gone to Steve's father's birthday, and Steve went to whatever event
Peter's at in New Zealand! <g>

 

[Van T. Dinh]

That's true ... maybe Steve's father will think Steve has gained a lot of
weight recently and won't know the swap ...

I think Peter is in NZ to set up a new computer network with all sorts of
customised routers / VPN, etc ... that links back to the main network in
Sydney so I am not sure Steve can handle network set-up ...

 

[MikeR]

I have an access application that uses a 3rd party OCX which is installed and
registerd in the windows/sytem32 folder.
Now the vendor has a new OCX with same name but is NOT binargy compatable. I
need to use it in the compile of my new application version.

Problem: when the new application installs and registers the OCX the old
version of the app fails

Customers want to install and try out new version of our app (buth then
thier old version is pooched) also they may install app anywhere but i'm
installing OCX in same windows/system32 folder.

Short of taking 3rd party vendor to woodshed for not making OCX binary
compatable else just renaming ocx what can I doo?

Thanks,
Sherwood

Google for "side by side dll" (w/o the quotes). Or here's a MS link.
http://msdn.microsoft.com/library/d...roc/base/dynamic_link_library_redirection.asp
Watch out for line wrap.
HTH,
Mike

 

[Guest]

since this is an MSACCESS application with a .mde extention (not an .exe) do
you know it it also works for access?

Thanks

------------------------------------------------

 

[MikeR]

since this is an MSACCESS application with a .mde extention (not an .exe) do
you know it it also works for access?

Thanks

No, sorry, I don't know.
Mike