What's Needed to Make Stand-Alone App?

[croy]

I'm using MS Access 2000 (9.x) to make a database app for a
local group that I do volunteer work for.

What would I have to acquire in order to turn this into a
stand-alone app. that they could use on a computer that
didn't have MS Access installed?

 

[Douglas J. Steele]

You'd need the Microsoft Office Developer Edition for 2000 (see
http://msdn.microsoft.com/en-us/library/Aa164865 ), but good luck in trying
to find it: Microsoft stopped selling it when Office 2002 was released.

On the other hand, you might be able to use the Office 2007 Runtime, which
is free. See http://msdn.microsoft.com/en-us/office/bb229700.aspx

 

[David-W-Fenton]

I'm using MS Access 2000 (9.x) to make a database app for a
local group that I do volunteer work for.

What would I have to acquire in order to turn this into a
stand-alone app. that they could use on a computer that
didn't have MS Access installed?

You'd need the Access runtime.

A2000 is a very old version (it was released in June 1999), and very
problematic (you really need to make sure it's patched to the
lastest service packs for it to be reliable), but an app created in
A2000 can be run in all versions since then.

The A2007/A2010 runtimes are free, but the ribbon interface can
cause issues. The A2003 runtime is not really available any more
(and it cost $$$). However, I've distributed one app developed in
A2003 with the A2007 runtime, but it was a kiosk-type app running on
a single workstation, and didn't need any toolbars or menus, so
hiding the ribbon didn't remove any functionality.

 

[croy]

You'd need the Microsoft Office Developer Edition for 2000 (see
http://msdn.microsoft.com/en-us/library/Aa164865 ), but good luck in trying
to find it: Microsoft stopped selling it when Office 2002 was released.

On the other hand, you might be able to use the Office 2007 Runtime, which
is free. See http://msdn.microsoft.com/en-us/office/bb229700.aspx

Thanks for the reply.


For that last option, if I have it correct, I could use
Access 2k to create an MDE, and then have someone who
doesn't have Access at all, download and install the
Runtime, and then dbl-clicking on the MDE would get them the
useable application?

Is it testable without having a non-Access machine at my
disposal?

Would installing the Runtime on my machine (that has MS
Access 2k installed) cause any sort of havoc?

 

[croy]

You'd need the Access runtime.

A2000 is a very old version (it was released in June 1999), and very
problematic (you really need to make sure it's patched to the
lastest service packs for it to be reliable), but an app created in
A2000 can be run in all versions since then.

The A2007/A2010 runtimes are free, but the ribbon interface can
cause issues. The A2003 runtime is not really available any more
(and it cost $$$). However, I've distributed one app developed in
A2003 with the A2007 runtime, but it was a kiosk-type app running on
a single workstation, and didn't need any toolbars or menus, so
hiding the ribbon didn't remove any functionality.

Thanks for reminding me about the Service Packs! A recent
HDD failure forced a re-install of everything, and I had
completely forgotten about the Office SPs. And there *have*
been a few of those head-scratching moments, since the
reinstall.

 

[Douglas J. Steele]

Thanks for the reply.


For that last option, if I have it correct, I could use
Access 2k to create an MDE, and then have someone who
doesn't have Access at all, download and install the
Runtime, and then dbl-clicking on the MDE would get them the
useable application?
Yes.

Is it testable without having a non-Access machine at my
disposal?

Would installing the Runtime on my machine (that has MS
Access 2k installed) cause any sort of havoc?

Why not use a virtual machine (Virtual PC, VM, etc.) to check?