will References stick in an MDE?

[deko]

If I create an MDE from an Access 2002 MDB, will the references "stick" when
the MDE is installed on other workstations?

For example:

I've created an MDB that requires certain References to be selected (in the
References dialogue of the Visual Basic editor window). If I convert this
MDB into an MDE (from Tools >> Database Utilities >> Convert Database), will
those references remain selected if I Zip the MDE and email to someone, and
then they install it on their workstation? Assuming they have Access 2002,
how will they modify the References for their installation, since this is an
MDE? Or, will they not need to modify any References?

Thanks in advance...

[Albert D. Kallal]

The references will stick, but the problem is that how do you know the
target pc has those actual refs?

In the case of stuff like word, Excel, Outlook etc, you can (and should)
remove the references and use late binding anyway. That way, if one of the
features (say, outlook) is not installed, your application will NOT break,
and continue to function.

So, for automation of the other office applications, you usually can, and
should use late binding.

However, yes, your references do stick, and stay in the mde. The challenge
is making sure that the target pc has those other library's. And, when
possible as mentioned, use late binding, so when even one thing is missing,
your applction can still function.

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[deko]

well, I suppose that's both good news and bad news.

The mdb in question does use references to Word, Excel and Outlook.

This may be a dumb question... but how do I implement late binding?
"Albert D. Kallal" <NO************@msn.com> wrote in message
news:ehElb.150882$pl3.119904@pd7tw3no...

The references will stick, but the problem is that how do you know the
target pc has those actual refs?

In the case of stuff like word, Excel, Outlook etc, you can (and should)
remove the references and use late binding anyway. That way, if one of the
features (say, outlook) is not installed, your application will NOT break,
and continue to function.

So, for automation of the other office applications, you usually can, and
should use late binding.

However, yes, your references do stick, and stay in the mde. The challenge
is making sure that the target pc has those other library's. And, when
possible as mentioned, use late binding, so when even one thing is missing, your applction can still function.

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn

[Albert D. Kallal]

"deko" <dj****@hotmail.com> wrote in message
news:Jv*****************@newssvr29.news.prodigy.co m...

well, I suppose that's both good news and bad news.

The mdb in question does use references to Word, Excel and Outlook.

This may be a dumb question... but how do I implement late binding?

The above is a good question.

http://www.vb-helper.com/tutorial_of...utomation.html

The most often cited reason to use early binding (ie: set ref in the
references) is one of performance. However, it is the load time, and the
launching of the application that is the performance hit, not the execution
of a few lines of vba code.

If you have complete control over the versions of word, and outlook and
excel, then you most certainly CAN use early binding. However, if you want
some version independence, or you want to be able to assume that one of the
office parts are NOT installed, then late binding is the ticket.
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
ka****@msn.com
http://www.attcanada.net/~kallal.msn