By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,870 Members | 2,484 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,870 IT Pros & Developers. It's quick & easy.

wshom.ocx license & distribution issues?

P: n/a
I am developing an Access Application for distribution to many users,
who will probably have different versions of Windows installed. I have
recently discovered iWshRunRimeLibrary, the windows Script Host Object
Model, which I can reference via wshom.ocx. My initial usage of it was
to facilitate easy Shortcut setup, but the more I look at it, the more
I see many other handy capabilities. Some of these I have already
implemented in code, in perhaps less elegant ways, but some offer me
new and useful capabilities.

My question has to do with licensing and distribution. Can I count on
wshom.ocx being on every windows system? Are there different versions
that could pose compatibility problems? Does perhaps one version work
with Access 2000, another with Access XP, etc? If it turns out that
one of my users does not have wshom.ocx on their machine for whatever
reason, or it is the wrong version, can I distribute the 'right
version' to them? I have purchased Office XP Developer, which entitles
me to distribute the Access Run-time, although at this point, I am
only working with Access 2000 and for the time being, my Users need to
have Access 2000 on their machines. Does my Office Developer give me
permission to distribute wshom.ocx or is it ok to distribute it
without it, anyway?

I'd like to hear from other Access developers and get their feedback
on wshom.ocx - is it reliable on different windows systems, any
pitfalls, etc. Thanks in advance for any insights.

Nov 13 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.