References in an MDE

[Stanley L.]

I am converting a AC 2000 to an AC2007 and adding a couple of new ActiveX
references. If I distribute an accde (equivalent of AC2000 MDE) application,
does the user need to be concerned about the references and their presence.
The thinking behind my question is that when a compiled version is made
aren't all the references included inside the compiled version? For example,
does an OCX used in many forms need to exist on the User's PC as an OCX file?
If so, I need to provide a routine for the user or application itself to
verify reference presence and integrity.
Thank you!
Stanley L.

 

[Rick Brandt]

I am converting a AC 2000 to an AC2007 and adding a couple of new
ActiveX references. If I distribute an accde (equivalent of AC2000
MDE) application, does the user need to be concerned about the
references and their presence. The thinking behind my question is
that when a compiled version is made aren't all the references
included inside the compiled version? For example, does an OCX used
in many forms need to exist on the User's PC as an OCX file? If so, I
need to provide a routine for the user or application itself to
verify reference presence and integrity.
Thank you!
Stanley L.

Recipe for trouble. Yes, the references come along with an accde (just as
they do in an MDB or MDE), but that is not the issue. The issue is when the
library file being referenced does not exist on the target machine. Your
app will fold up like a cheap lawn chair.

The library is not "rolled into" your file. All it contains is the pointer
to where it thinks the file should be. When it's not there you get errors.

You must have a license that allows you to distribute your ActiveX controls
and include them with your file in a proper installation package.

 

[Stanley L.]

Thank you Rick. The lawn chair folding puts it all into perspective....cute
The ActiveX's are purchased and allow re-distribution with applications. I
appreciate your time, effort and expertise. Thanks again!
Stan L.

 

[Tony Toews [MVP]]

I am converting a AC 2000 to an AC2007 and adding a couple of new ActiveX
references. If I distribute an accde (equivalent of AC2000 MDE) application,
does the user need to be concerned about the references and their presence.
The thinking behind my question is that when a compiled version is made
aren't all the references included inside the compiled version? For example,
does an OCX used in many forms need to exist on the User's PC as an OCX file?
If so, I need to provide a routine for the user or application itself to
verify reference presence and integrity.

Just curious. What ActiveX controls? Maybe we can suggest some
alternatives.

How do you get rid of troublesome ActiveX Controls/references?
http://www.granite.ab.ca/access/referencetroubles.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/