Re: What changes to I make to a computer that will allow it to run

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

As I remember, the original problem is the diversity of Access versions in
your office. If everyone has the same version of Access, this is not a
problems. With the mix you have, you are going to have errors and problems
and things that don't work correctly.

The solution is to get everyone on the same version of Access. So, that
means you have to purchase a copy of Access 2003 for everybody or you can
purchase the Developers Toolkit. The Toolkit creates a setup.exe file that
includes the runtime version of Access 2003. The setup.exe you build will
include your mdb or mde (preferred), the Access runtime, and any other files
you need to include, such as DLL files needed by your application. This is
the only way you can legally deliver a runtime version of Access.

So, in short, there are two ways:
1. Get every user a copy of Access 2003
2. Get the Developer's Toolkit
"Margaret Bartley" wrote:

> I don't recall doing anything like that with the A2K version, I just created
> an .mde, and she was able to run it on her computer. Did someone, earlier,
> that she didn't remember, install the runtime version of Access 2000 on her
> machine? Or is this a background process that takes care of itself, the
> first time, but then I need to do some maintenance when an executable from a
> different version of Access in put on the users' machines?
>
> Is this a separate process? I've only ever handed the users the executable,
> and never had to worry about installing anything on their machines.
>
> Is there any documentation for this?
>
> Thank you,
> Margaret
>
>
> "Klatuu" <Klatuu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:65C1F67B-2547-46CC-A394-5B55697C558F@xxxxxxxxxxxxxxxx
> > Rick's Information is correct. I would suggest you get your boss to
> > acquire
> > the 2003 Office Developer's Kit. With it, you will be able to create a
> > setup.exe file that will install the mde, the 2003 runtime, and any other
> > support files needed by your application.
>
> >
> > "Margaret Bartley" wrote:
> >> I guess, the better question would be:
> >> What do I do to my boss's machine that will allow it to run an Access
> >> 2003
> >> mde, once it's run an A2K .mde?
> >>
> >>
> >>
>
>
>
.

Relevant Pages

  • Re: What changes to I make to a computer that will allow it to run an
    ... I don't recall doing anything like that with the A2K version, ... an .mde, and she was able to run it on her computer. ... install the runtime version of Access 2000 on her ... Or is this a background process that takes care of itself, ...
    (microsoft.public.access.modulesdaovba)
  • Re: differences beween runtime and regular database, why do I get errors?
    ... try running the mde and a shortcut with the /runtime on your machine. ... it is not a clean machine anymore. ... I find VPC really helps a lot as you can then test the runtime install ...
    (microsoft.public.access.devtoolkits)
  • RE: Urgent: Securing My Access from Piracy
    ... machine or try to install it on another machine using the same password and ... Now when I give it to tham I will make an MDE. ... >> HTH ... >> Martin J ...
    (microsoft.public.access.security)
  • Re: Vista Virtual Store - File Versioning
    ... I install an MDE file to Program Files. ... Install the FE MDE to the user specific folder such as CSIDL_APPDATA ... Tony Toews, Microsoft Access MVP ...
    (microsoft.public.access.setupconfig)
  • Re: MDE-File
    ... A main database ... >> When I install the runtime-version, ... And they should be the same for mdb as mde, ... >> refresh the link and use dbHiddenObject to hidden IT. ...
    (microsoft.public.access.developers.toolkitode)