MS Office 2000 Developers Edition

  • Thread starter Thread starter Chris Sergent
  • Start date Start date
C

Chris Sergent

Hi,
I work for the state of Illinois and we would like to
distribute runtime MS Access databases. Some staff believe
this makes other versions corrupt upon install. I would
like to locate documentation as to refute this claim. Any
information regarding this would be greatly appreciated as
well as information that is agreement. Please, no
statements, only references of actual documentation as
this would be needed to avoid possible purchases for
software made unneccessarily.

Thanks in advance.

Chris Sergent
(e-mail address removed)
 
Quite frankly, I would take some 1st hand knowledge by some who contribute
to these newsgroups over Microsoft documentation.
 
There are of course potential problems with installing
MS Office on MS Windows, and using a runtime licence
does not make you immune to these. A good place to
start searching for documentation on these is Google:

www.google.com.au

This will help you find some KB articles about overcoming
common installation problems.

Also, the install scripts built with ODE 2000 are not
very robust: for News Group articles referring to this
you should google:

microsoft.public.office.access.devtoolkits
and
microsoft.public.access.developers.toolkitode

The web addresses that you get are static, and you
can refer to them again if you need to.

For basic information about the runtime licence, you should
also read the Access Help information about 'runtime'

I'm not sure what else you can expect: surely you
aren't expecting a MS white paper that states:
"MS Access Runtime installation does not make other Versions Corrupt" ????

BTW: the MS Office 2000 Developers Edition is unsupported,
and has been withdrawn as part of the Java settlement.
Google will help you find the statement from MS.

(david)
 
As someone else already mentioned, the 2000 stuff is no longer available. It's actually 2 versions old now. Unless you already have
it, you'll need to look at the "Microsoft Office Access 2003 Developer Extensions" to get the Access run-time license now. See
http://msdn.microsoft.com/office/technologyinfo/devtools/accessextensions/default.aspx.

For some thoughts on run-time installations, Tony has a lot of good info and links at http://www.granite.ab.ca/access/runtime.htm.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
Chris Sergent said:
Hi,
I work for the state of Illinois and we would like to
distribute runtime MS Access databases. Some staff believe
this makes other versions corrupt upon install.
Click to expand...

You have to remember that installing the runtime is still much the same as
installing ms-access on those machines.
I would
like to locate documentation as to refute this claim.
Click to expand...

The question you are actually asking is:

Do problems exist when you install another version of ms-access on a
existing pc? The answer is most certainly yes. The fact of the matter,
installing the runtime is really the same as installing ms-access. (there is
only few things removed...but for all intensive purposes...you ARE
INSTALLING ms-access).

So, we don't need some supporting document. Armed with the knowledge that
the runtime is really the same as installing ms-access, then we ONLY have to
ask is there a problem when you install more then one version of ms-access
on a pc? The answer is yes!

That install can be up to 150 megs in size, and adds in the neighbourhood of
1000+ entries in the registry. It is a very large install, and one that is
normally part of office.

Of course, when you use the runtime, then you also have to provide the menu
bars and user interface. (on the other hand..any good developer thinking of
distributing their software no doubt hid the ms-access interface a LONG LONG
time ago...else one could not possibly be thinking of distributing some
software...right?). And, I sure you always distribute a split database (and,
of course always a mde..right?). I am just saying that if you have not had a
good amount of developer time hiding the access interface, and doing the
basic stuff like providing code to "re-link" your split database..then you
are much like a first year med student wanting to do brain surgery. You are
not ready for that step yet!

Assuming that you have all the above done (and a lot more), then if you are
planning to distribute your application to a lot of machines I would
consider purchasing a good installer AND ALSO purchases some scripts from
www.sagekey.com. Purchasing the scripts from sagekey will turn out to be a
bargain in terms of reduced support costs.

sagekye can also supply scripts for the MSI (Microsoft installer),so you can
save the cost of having to purchase a installer..and only need the scripts.
(windows 2000, and later usually has the MSI). If you need to install on
early versions of windows (win98)..then I would purchase a commercial
installer and then purchase the scripts for that installer from sagekey.

You can see the list of problems the above fixes.

http://www.sagekey.com/products/acc2000/msi.asp

Here is a great article and some reading

http://www.sagekey.com/whats/article.asp
 
I'm not sure exactly what you're looking for, Chris - 'documentation' is a
rather broad term - in a sense, anything that anyone posts here could be
called 'documentation'. If you mean documentation published by Microsoft,
you'll find that in the Knowledge Base (click 'Support' and then 'Knowledge
Base' at www.microsoft.com)

Problems can arise when installing *any* software. I'm not sure if there are
actually more installation problems with the runtime than with retail
Access, but when problems do arise with the runtime, they are, in my
experience, considerably more difficult to troubleshoot and resolve. Whether
the cost of the extra licences outweighs the reduced support costs is a
question you'll need to decide based on your best estimate of the support
costs versus the cost of the extra licences.
 
I'm not sure what else you can expect: surely you
aren't expecting a MS white paper that states:
"MS Access Runtime installation does not make other Versions Corrupt" ????
Click to expand...

I think my message was ruder than I intended. I regret that.

(david)
 
Back
Top