By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,679 Members | 2,036 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,679 IT Pros & Developers. It's quick & easy.

Using Access 2003 package wizard to package a database for a Access 2000 client

P: n/a
I developed an access database in access 2003(keeping my database in
the access 2000 format). It has been fully tested to be access 2000
compatible and works great.

I am trying to package the final version however and when I tell it to
create a shortcut it includeds the path to access 2003 in the shortcut
C:\Program Files\Microsoft Office\OFFICE11\

my client is running access 2000. I could not figure any way to change
the access application folder loction in the access setup. it is
assuming that since I have access 2003 the user of the appliaction does
too.

is there any way to fix this and still use the package wizard?

Nov 13 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
This begs the question why would you need the runtime for this user if they
already got a version of ms-access?

Why not just email them the file, or perhaps use WinZip (it can remember the
directory you zip to, and even create it for you.). In fact, you can create
a self extracting zip file, and it will be a zillion times smaller then
suing the package and deployment wizard to JUST TRANSFER a mdb file to that
user.

Unless the end user needs the a2003 runtime, then I see no reason at all to
use the package wizard. Just zip and email the person the file!! You are not
installing the runtime here, and obviously you don't need it...so I think
you got the wrong tool here to just send a person a simple mdb file, and
they already got ms-access installed (and, worse, a different version). You
cannot effectually use, and install the a2003 runtime on machines that have
other versions of ms-access without some problems. Remember, while we call
it the runtime, it is in fact installing ms-access on the users machine, and
if you run different versions, then you do ask for more trouble..

I would either force the user to start using a2003 (or your runtime which
you can include for free), or just dump the use of the package wizard and
all the incredible complexities you are using here to simply transfer a mdb
file to that users computer.

You could perhaps try making a mdb install with the package wizard, and NOT
include the runtime files. This would *kind* of get you the same idea as
simply using WinZip to transfer the mdb file only..and NOT install the
runtime. This would of course only let you copy files..and would not setup
shortcuts. To make the shortcuts, you might as well just zip up the shortcut
for the user and send that....

I just don't see the need in this case to use the p&d, especially for a user
with a different versions of ms-access, and you are trying to transfer a mdb
file that is for a different version. The p&d for a2000 is for a2000 files.
the p&d for a2002 is for a2002 files,and the p&d for a2003 is for a2003
files.

I suspect perhaps there is something here I am missing, or misunderstanding.
Please do feel free to expand on your question, as I might not be grasping
what you are trying to do?
..

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #2

P: n/a
This begs the question why would you need the runtime for this user if they
already got a version of ms-access?

Why not just email them the file, or perhaps use WinZip (it can remember the
directory you zip to, and even create it for you.). In fact, you can create
a self extracting zip file, and it will be a zillion times smaller then
suing the package and deployment wizard to JUST TRANSFER a mdb file to that
user.

Unless the end user needs the a2003 runtime, then I see no reason at all to
use the package wizard. Just zip and email the person the file!! You are not
installing the runtime here, and obviously you don't need it...so I think
you got the wrong tool here to just send a person a simple mdb file, and
they already got ms-access installed (and, worse, a different version). You
cannot effectually use, and install the a2003 runtime on machines that have
other versions of ms-access without some problems. Remember, while we call
it the runtime, it is in fact installing ms-access on the users machine, and
if you run different versions, then you do ask for more trouble..

I would either force the user to start using a2003 (or your runtime which
you can include for free), or just dump the use of the package wizard and
all the incredible complexities you are using here to simply transfer a mdb
file to that users computer.

You could perhaps try making a mdb install with the package wizard, and NOT
include the runtime files. This would *kind* of get you the same idea as
simply using WinZip to transfer the mdb file only..and NOT install the
runtime. This would of course only let you copy files..and would not setup
shortcuts. To make the shortcuts, you might as well just zip up the shortcut
for the user and send that....

I just don't see the need in this case to use the p&d, especially for a user
with a different versions of ms-access, and you are trying to transfer a mdb
file that is for a different version. The p&d for a2000 is for a2000 files.
the p&d for a2002 is for a2002 files,and the p&d for a2003 is for a2003
files.

I suspect perhaps there is something here I am missing, or misunderstanding.
Please do feel free to expand on your question, as I might not be grasping
what you are trying to do?
..

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #3

P: n/a
you are totally correct. Since I am not including the runtimes the
packager is overkill. However my client needs me to provide him with
an install file as he uses a program called zenworks to push it to the
desktops. the users have zero access to their C: drives.

I can just zip the .mdb however then I dont see a way to create the
listing for my application in the program menu. The whole reason I was
using the packager was to get the program listed in the program menu.
I know I can make shortcuts but I dont know any way to get it listed in
the program menu.

Nov 13 '05 #4

P: n/a
you are totally correct. Since I am not including the runtimes the
packager is overkill. However my client needs me to provide him with
an install file as he uses a program called zenworks to push it to the
desktops. the users have zero access to their C: drives.

I can just zip the .mdb however then I dont see a way to create the
listing for my application in the program menu. The whole reason I was
using the packager was to get the program listed in the program menu.
I know I can make shortcuts but I dont know any way to get it listed in
the program menu.

Nov 13 '05 #5

P: n/a
Hey, you got a good answer!!

May I suggest in place of WinZip, you use the free inno installer.

It don't have a wizard to makes things easy..but the resulting install file
*should* be able to be pushed out via zenworks.

You can find more about the free inno installer here:

http://www.jrsoftware.org/isinfo.php

I have not used it, but have heard nothing but 100% praise for the
installer..

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #6

P: n/a
Hey, you got a good answer!!

May I suggest in place of WinZip, you use the free inno installer.

It don't have a wizard to makes things easy..but the resulting install file
*should* be able to be pushed out via zenworks.

You can find more about the free inno installer here:

http://www.jrsoftware.org/isinfo.php

I have not used it, but have heard nothing but 100% praise for the
installer..

--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pl*****************@msn.com
http://www.members.shaw.ca/AlbertKallal
Nov 13 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.