Results 1 to 5 of 5
  1. #1
    New Lounger
    Join Date
    Mar 2001
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Packaging an Access DB (Access 2002)

    I am wondering if anyone has ever had to "package" an access db. I am not sure if that is the proper terminology but basically what I need to do is to provide a client with an access db I have designed (and populated with data) that can be installed like any other program. I would love to be able to send out an .exe program that you know, actually looks like a professional product! Can the MS developer edition do this? Thanks <img src=/S/crazy.gif border=0 alt=crazy width=15 height=15>

  2. #2
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Packaging an Access DB (Access 2002)

    The developer edition can be used to create a setup package. The setup uses an executable, but you still wind up installing an mdb (or mde) file on the target machine. In fact, if you want it to work on the target machine, the only safe way to do it is by creating a setup.

    I don't recommend the wizard that comes with Office Developer though, not if you're giving it to a client. You have to have the Developer edition in order to have a license to distribute the Access runtime files and some of the other libraries that it may use, but if you rummage around in this forum you'll find lots of discussions on this and on why the Wise Installer or InstallShield with SageKey scripts are the preferred tools for packaging Access apps. I gave up on the wizard years ago when I discovered that my setup didn't install properly on a machine with a different version of Windows. The client was nearly 200 miles away, so I couldn't drop by and fix it. I saw a similar thing a couple of years ago when I was contracting for a federal agency. They also learned the hard way that the wizard was worthless for what they needed to do.
    Charlotte

  3. #3
    New Lounger
    Join Date
    Mar 2001
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Packaging an Access DB (Access 2002)

    Thanks Charlotte. How complicated is it to package an access application? I am not really a developer, more a power access user . I have developed this access db, maintain and improve it and really need to take it to that next level. What specific software programs would I need to get? I took a look at the installshield website and was immediately aware of how much I don't know <img src=/S/brickwall.gif border=0 alt=brickwall width=25 height=15> . And what do the sagekey scripts do?

  4. #4
    Plutonium Lounger
    Join Date
    Dec 2000
    Location
    Sacramento, California, USA
    Posts
    16,775
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Packaging an Access DB (Access 2002)

    The SageKey scripts save you from having to create the scripts yourself. They control how the installation proceeds and how it handles the situations it encounters. They come from a separate company from than the installer products themselves.
    Charlotte

  5. #5
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Brisbane, Queensland, Australia
    Posts
    352
    Thanks
    0
    Thanked 1 Time in 1 Post

    Re: Packaging an Access DB (Access 2002)

    I think one thing you need to decide is whether your client will have access installed, and whether it is the same version you are using. If your client has the same version of access you should be able to just send the MDB or MDE (if you want to hide the code). The main issue will be if references need to be set.

    If your client does not have access or has a different version you will need to package a runtime edition of access. That means you have to have developer. You can package using developer wizard and look at a thread here on MDAC which the packager does not necessarily pick up. but you will need to have access to a test machine without Access installed to make sure the package works. Preferably the test machine should have the same OS and general set up as your client's machine.
    David Grugeon
    Brisbane Australia

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •