Front End Loosses link to control - Please help!

[Gary]

I tried posting this on "microsoft.public.access.setupconfig" with no help.
So i'm trying here.

I am losing my link to an ocx control when I deliver a new FrontEnd

I have a system with FrontEnds and a Backend on the server.
ForntEnd PC's are running WinXP(home) & Win2000

I develop my Frontend on a standalone pc NOT connected to the network.
I have an OCX control that I have registerd on my standalone PC
located in the same directory as my Frontend (C:\MyApplication)
All Networked PC's have the same directory wich is where their
Frontend and ocx control reside. So it's the same as my development PC

I am using Tony Toews AutoFE updater to deliver the FrontEnd.
So I copy my New version of the FrontEnd to the Network for the
users to download to their PC's.
That's when the link to the OCX control is lost and
I have to go to each PC and reconnect the Control.

What must I do to avoid haveing to goto each PC just to configure
the control everytime I deliver a New FrontEnd.

Thanks for any Help.

 

[Gary]

Isn't Anybody able to respond?......

 

[Allen Browne]

Welcome to DLL hell.

You will need to ensure the ocx is registered in the Windows Registry on
each computer, using something like:
regsvr32 "c:\MyFolder\MyControl.ocx"
and this will have to be done before you execute any code that could attempt
to reference the library.

For an introduction to that idea, see michka's article:
How to guarantee that references will work in your applications
at:
http://www.trigeminal.com/usenet/usenet026.asp?1033

The whole issue of broken references is so annoying, that I personally avoid
any references I don't absolutely need, often getting it down to just 3.
Perhaps the deafening silence in response to your posts means that others
are not keen on ocx's either.

 

[Denny Walsh]

Thanks Very much for the reponse Allen. Sincerely!

You will need to ensure the ocx is registered in the Windows Registry on
each computer, using something like:
regsvr32 "c:\MyFolder\MyControl.ocx"
and this will have to be done before you execute any code that could
attempt to reference the library.

Does this have to be done only once? Or EVERY TIME I
deliver a new version of my FE?
If thats the case I'll remove the OCX.
BTW: the OCX is the zMousetrap.ocx

 

[Allen Browne]

The ocx should only have to be registered once, unless there is ANY change
to the ocx (e.g. different version), and then it would need to be registered
again.