Whay do I need to deploy for my references?

[Max Moor]

Hi All,
I have an Access 2002 app I want to deploy. I have Office developer,
and I know what all my references are (listed below). Because of
customization issues, I've chosen an installer other than Windows' (Tarma).

My question is whether or not there is a site, book, or other
reference that can tell me what I need to ship, other than Access Runtime,
to meet all my reference needs?

In some cases, like with 'MouseWheel', it's obvious. With others,
like 'Microsoft Office 10.0 Object Library' what do I ship?

Any pointers would be appreciated.

- Max






My References:

Visual Basic For Applications
Microsoft Access 10.0 Object Library
OLE Automation
Microsoft ActiveX Data Objects 2.5 Library
Microsoft ADO Ext. 2.8 for DLL and Security
Microsoft DAO 3.6 Object Library
Microsoft Office 10.0 Object Library
RTF2 ActiveX Control module
HHCtrl 4.0 Type Library
MouseWheel

 

[Guest]

like 'Microsoft Office 10.0 Object Library' what do I ship?

Microsoft Office 10.

If you don't want to pay for a copy of Office for every client,
you could specify that the application will only run if Office 10
is installed.

Or, better, remove the reference to Office 10. It's only there
for debug and development, and to make it run a tiny unnoticeable
amount faster.

After you remove the Office reference, you will have to change
any declaration that specifically references it, to use general
'object' declarations:
dim MyMenu as object
and explicit numbers instead of named constants.

Just remove the reference and fix what breaks. Do the same for
other references. Leave the VBA, Access, and ADO/DAO
references. Your application won't run unless Access is installed:
You will either have to specify the Access is required, or ship
a copy of Access (retail or runtime) with every copy.

(david)

 

[Tom Wickerath]

Hi Max,

For Office 10, look for a file named MSO.dll. For example, on my PC, this
file is located here:

C:\Program Files\Common Files\Microsoft Shared\Office10\MSO.dll

Here is a reference that you might find helpful:
How To Obtain Built-In Constant Values for an Office Application
http://support.microsoft.com/?id=239930


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Guest]

C:\Program Files\Common Files\Microsoft Shared\Office10\MSO.dll

"However, these files are not redistributable and must not be deployed
to a system that already has Microsoft Office 97, Office 2000, Office XP,
or Office 2003 installed."

"Not redistributable" means that you do not have permission to 'ship'
these files.

"Must not" means that if you 'ship' this file, you may break the clients
installation of MS office. The client will not thank you for that.

(david)

 

[Tom Wickerath]

Hi David,

That's very true. I was just trying to point out which file that a checked
reference to the "Microsoft Office 10.0 Object Library" references, not the
legalities in how/when/why you distribute certian files.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Max Moor]

Microsoft Office 10.

If you don't want to pay for a copy of Office for every client,
you could specify that the application will only run if Office 10
is installed.

Or, better, remove the reference to Office 10. It's only there
for debug and development, and to make it run a tiny unnoticeable
amount faster.

After you remove the Office reference, you will have to change
any declaration that specifically references it, to use general
'object' declarations:
dim MyMenu as object
and explicit numbers instead of named constants.

Just remove the reference and fix what breaks. Do the same for
other references. Leave the VBA, Access, and ADO/DAO
references. Your application won't run unless Access is installed:
You will either have to specify the Access is required, or ship
a copy of Access (retail or runtime) with every copy.

(david)

Where have you been???
I've been fighting a bug in my installation, that seemed related to my
trying to ship a stripped down version of Office 10 so this reference would
be happy.
Aside from the fact that I didn't realize that I was trying to do
something illegal (shipping Office 10), the bug made the installation
computers' internet browser not work, and made system restore show a blank
screen!
As for my app, the ONLY thing that broke when I took the reference out
was a menu bar object reference I used to disable a menu item. I changed
it to a generic object, as you suggested, and it works just fine.
My bug is gone, I have one less reference to track, and my installer is
30% smaller.
It's been a long time ago that I first started this project, and I'm
not sure where the Office 10 reference came from in the first place. I
sure didn't know I could get rid of it, though.

Thank you so much!

- sMax