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

Access 2002 runtime error for Windows XP

P: n/a
Apologies in advance as I am SURE this has been asked 100 times - but I
haven't got a simple answer:

I have MS Office XP Developer and have created an installation package (with
the runtime) for an Access 2002 database.

The problem: when installing on a Windows XP machine, I get the following
error:

The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.
I have updated the XP Developer SR-1, that I thought would fix any problems
(including any packaging wizard stuff).

I re-created the package/runtime and get the same error.

Any ideas?
TIA,
Aliza
--
-----------------------------------
Aliza Klein
ab*****@optonline.net
-----------------------------------
Nov 13 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Hi Aliza,
Check this out:
http://support.microsoft.com/?id=837150

Regards,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:IY****************@fe08.lga...
Apologies in advance as I am SURE this has been asked 100 times - but I
haven't got a simple answer:

I have MS Office XP Developer and have created an installation package (with the runtime) for an Access 2002 database.

The problem: when installing on a Windows XP machine, I get the following
error:

The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.
I have updated the XP Developer SR-1, that I thought would fix any problems (including any packaging wizard stuff).

I re-created the package/runtime and get the same error.

Any ideas?
TIA,
Aliza
--
-----------------------------------
Aliza Klein
ab*****@optonline.net
-----------------------------------

Nov 13 '05 #2

P: n/a
Hi, Barry.

Thanks for pointing me in the right direction, I really appreciate it!

One follow up questions (if you happen to know):

Is this a permanent change I should make, or only for XP SP2 and Win 2003
installations?

If I make the change, will the installation now NOT work on previous
versions (98, 2000 etc.)?

Do I now need to be distributing different installations based on the OS?

TIA,
Aliza

"Barry Wright" <ba*****************@NOSPAMrogers.com> wrote in message
news:jb********************@rogers.com...
Hi Aliza,
Check this out:
http://support.microsoft.com/?id=837150

Regards,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:IY****************@fe08.lga...
Apologies in advance as I am SURE this has been asked 100 times - but I
haven't got a simple answer:

I have MS Office XP Developer and have created an installation package

(with
the runtime) for an Access 2002 database.

The problem: when installing on a Windows XP machine, I get the following error:

The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.
I have updated the XP Developer SR-1, that I thought would fix any

problems
(including any packaging wizard stuff).

I re-created the package/runtime and get the same error.

Any ideas?
TIA,
Aliza
--
-----------------------------------
Aliza Klein
ab*****@optonline.net
-----------------------------------


Nov 13 '05 #3

P: n/a
Hi Aliza,

Basically, it is through trial and error; below has worked for me.

I ususally make four installation packages for any MS Access database I
deploy:
If the user does NOT have MS Access 2000 or above installed:
1) Make an installation package with RunTime but without System Components.
2) Mak an installation package with RunTime and with System components.
I get the user to install 2 if 1 tells them to upgrade System Components. So
1 should install OK onto an Xp OS with SP2.

If the user does have MS Access 2000 or above installed:
1) If they have MS Access on the computer I install by making a simple zip
exe which includes the Access Database (mdb), and Workgroup Information File
(mdw), a desktop shortcut with all the Commandline Parameters and any other
file, i.e., your help file if you make one.
2) An installation package without RT and without System Components.
If they have MS Access 2000 or greater I just use Package 1 (zip exe) to
install.

If you have tried to deploy an Access 2000 database using the 2002 package
you will find that you need to point to the WIF (mdw) instead of the actual
mdb file. You then need to modify the Startup Commandline according.

Good luck,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:En*****************@fe08.lga...
Hi, Barry.

Thanks for pointing me in the right direction, I really appreciate it!

One follow up questions (if you happen to know):

Is this a permanent change I should make, or only for XP SP2 and Win 2003
installations?

If I make the change, will the installation now NOT work on previous
versions (98, 2000 etc.)?

Do I now need to be distributing different installations based on the OS?

TIA,
Aliza

"Barry Wright" <ba*****************@NOSPAMrogers.com> wrote in message
news:jb********************@rogers.com...
Hi Aliza,
Check this out:
http://support.microsoft.com/?id=837150

Regards,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:IY****************@fe08.lga...
Apologies in advance as I am SURE this has been asked 100 times - but I haven't got a simple answer:

I have MS Office XP Developer and have created an installation package

(with
the runtime) for an Access 2002 database.

The problem: when installing on a Windows XP machine, I get the following error:

The Office System Pack cannot be installed on this system because it
requires Windows NT 4.0 Service Pack or Later.
I have updated the XP Developer SR-1, that I thought would fix any

problems
(including any packaging wizard stuff).

I re-created the package/runtime and get the same error.

Any ideas?
TIA,
Aliza
--
-----------------------------------
Aliza Klein
ab*****@optonline.net
-----------------------------------



Nov 13 '05 #4

P: n/a
The real question, I guess is - why doesn't the Packaging Wizard actually
take care of all this stuff!

Thanks for all the help - it is appreciated!
Aliza

"Barry Wright" <ba*****************@NOSPAMrogers.com> wrote in message
news:bo********************@rogers.com...
Hi Aliza,

Basically, it is through trial and error; below has worked for me.

I ususally make four installation packages for any MS Access database I
deploy:
If the user does NOT have MS Access 2000 or above installed:
1) Make an installation package with RunTime but without System Components. 2) Mak an installation package with RunTime and with System components.
I get the user to install 2 if 1 tells them to upgrade System Components. So 1 should install OK onto an Xp OS with SP2.

If the user does have MS Access 2000 or above installed:
1) If they have MS Access on the computer I install by making a simple zip
exe which includes the Access Database (mdb), and Workgroup Information File (mdw), a desktop shortcut with all the Commandline Parameters and any other file, i.e., your help file if you make one.
2) An installation package without RT and without System Components.
If they have MS Access 2000 or greater I just use Package 1 (zip exe) to
install.

If you have tried to deploy an Access 2000 database using the 2002 package
you will find that you need to point to the WIF (mdw) instead of the actual mdb file. You then need to modify the Startup Commandline according.

Good luck,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:En*****************@fe08.lga...
Hi, Barry.

Thanks for pointing me in the right direction, I really appreciate it!

One follow up questions (if you happen to know):

Is this a permanent change I should make, or only for XP SP2 and Win 2003
installations?

If I make the change, will the installation now NOT work on previous
versions (98, 2000 etc.)?

Do I now need to be distributing different installations based on the OS?
TIA,
Aliza

"Barry Wright" <ba*****************@NOSPAMrogers.com> wrote in message
news:jb********************@rogers.com...
Hi Aliza,
Check this out:
http://support.microsoft.com/?id=837150

Regards,
Barry

"Aliza Klein" <ab*****@optonline.net> wrote in message
news:IY****************@fe08.lga...
> Apologies in advance as I am SURE this has been asked 100 times - but
I > haven't got a simple answer:
>
> I have MS Office XP Developer and have created an installation

package (with
> the runtime) for an Access 2002 database.
>
> The problem: when installing on a Windows XP machine, I get the

following
> error:
>
> The Office System Pack cannot be installed on this system because it
> requires Windows NT 4.0 Service Pack or Later.
>
>
> I have updated the XP Developer SR-1, that I thought would fix any
problems
> (including any packaging wizard stuff).
>
> I re-created the package/runtime and get the same error.
>
> Any ideas?
> TIA,
> Aliza
>
>
> --
> -----------------------------------
> Aliza Klein
> ab*****@optonline.net
> -----------------------------------
>
>



Nov 13 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.