Re: Creating Acces Application

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

2002: You'll need to install 2 CD's in order, all part of "Developer" package:
Office XP Professional
Office XP Developer
(Plus, in my version, an XP Developer Windows Component Update CD)
(Plus, sigh, SP updates obtained from MS site, though the first 2 CD's should
get it working they are not service-packed)

If you dont have those CD's, then it may not be Office Developer.

Once installed, open any database, Alt F11 or get to the code Window,
Add-In's, and you should see "Packaging Wizard".

There have been some reports (not sure which version) of the "Packaging
Wizard" not being there. All I can say is that in the 2 times I've done a full
Office XP Developer install, as above, it has been!

If you've used a previous wizard, each new version may take some getting used
to. Some of us might consider the description "nice interface" as subjective!
(but yes it's the one that does what you say, except that you still have to
load Access-Runtime Access-via the Packaging Wizard if they don't already have
AccessXP)

Chris

"Jan" <vdykj@xxxxxxxxx> wrote in message
news:4AE0801D-E76D-4DC5-87D7-EE1973EAF391@xxxxxxxxxxxxxxxx
Hi Chris

Sorry for being unclear. I would like to comipile a runtime application of
my database that I can install on other PC's without having to load Access
on
them first.

I have managed to do this in the past and I am very sure I have used the
wizard that had a nice interface from where one need to select all all .mdb
files, an icon, network or floppy drive installation files, etc. I have
re-installed the Office on my new laptop and I am not sure if I have left
that part out by accident, or if I am just looking at the wrong place for
it.
Can you give me some direction please?

"Chris Mills" wrote:

That's a fairly broad question, Jan!

Perhaps you could say where you're coming unstuck, or do you not really
know
where to start?

Firstly, there are differences between Runtime and Full Access, and you
should
test your app by simulating runtime environment with a shortcut that
includes
the option /runtime. To do any development, you need to remove the option
or
have another shortcut.
See:
http://support.microsoft.com/default.aspx?scid=kb;en-us;208730
ACC2000: Differences Between Retail and Run-Time Microsoft Access
(will be similar for later versions)

Assuming you have it running OK in runtime mode, then you want to package
it!
Assuming you have installed Developer, Alt F11 or get to the code Window,
Add-In's, Packaging Wizard.

There's a plethora of issues (bugs) with the Package and Deployment
Wizard,
which is why many people choose other packagers like www.sagekey.com, but
the
PDW should basically work for a standalone installation.

You might like to post back with more specific questions.
Chris


"Jan" <vdykj@xxxxxxxxx> wrote in message
news:417213BC-2EDA-442A-8F7C-2074ED289E67@xxxxxxxxxxxxxxxx
I have a Microsoft Developers package, but I have not used the tool
(wizard)
to create a stand-alone access database with Office 2002. Can someone
please
give me some guidence??





.

Relevant Pages

  • RE: Deploying Access2002 app to XP with Office 2003
    ... I modified the ospfilelst.txt file (located in the Packaging ... I use the Office Developer packaging wizard. ... >> I have just run into a situation where my install no longer works. ... I receive an error saying the Office System Pack cannot be installed ...
    (microsoft.public.access.devtoolkits)
  • Re: Access runtime packaging error
    ... Developer has its own SP updates, and they're separate from the Office SP ... > I am packaging with MS Office Developer XP with its SP3> installed and another SP for runtime - all that MS> thought I should install. ...
    (microsoft.public.access.developers.toolkitode)
  • Re: Modify shortcut in installer MSI file
    ... According to a recent post by Adam Ulrich (Microsoft Test Manager), ... Package & Deployment Wizard of Access 2003 is not to be taken as a serious ... > I am in the process of packaging my application with the 2003 packaging ... mdb and then change the setup files so the icon paths are correct. ...
    (microsoft.public.access.developers.toolkitode)
  • DATE/TIME ERRORS
    ... I have Office XP Developer on my PC using Windows XP. ... before packaging with the Packaging Wizard, ... expression in table-level validation expression." ...
    (microsoft.public.access.modulesdaovba)
  • Re: Access 2003 PDW issue
    ... I'm building a setup using the 2003 packaging ... > wizard. ... > them to both have start-up icons. ...
    (microsoft.public.access.devtoolkits)