Access Xp Packager Install Error (Office Xp Developer)

Topic

New Reply

We have packaged a database using the Office Xp Developer Packaging Wizard. When we install it on a target machine that contains Office 97 we get the following error:

“The Office System Pack cannot be installed on this system because the languages are no the same. Install the Office System Pack for the appropriate language on your computer. For assistance contact your application provider.”

Nice of Murkysoft to blame us for the problem!

The regional settings on the packaging and target machines are the same. We have also made sure that the language for the Office Xp on the packaging machine matches the target machine (English Australian – whatever that is!).

Any gueses as to what the error message really means? Is it talking about world languages or programming languages (eg VB6.0 etc).

Reply | Quote

Replies

Did you include the Access runtime with the setup? If not, that may be what it’s looking for. The Packaging Wizard, under all its various versions and names, has been a pathetic add-in for building serious installs.

Reply | Quote

Oh Yeah! The funny thing is that it installs and runs perfectly well on a newly formatted machine but not on one that has Office 97 installed. I can’t guarantee that this is the only difference. We have tried running VB6 update on the target but it doesn’t help. The target machine has ie6 on it so it shouldn’t be an ie version problem. I wish ie was only an internet browser and not half a flaming operating system.

Do you use the packaging wizard or do you have a better way of doing it?

Reply | Quote

I opt for InstallShield Express for my own use, but my employer uses Wise with SageKey scripts. You have much more control over the whole setup that way and can do things like create desktop shortcuts, display a EULA, etc., without tearing your hair out or giving up in despair. Using a 3rd party installer costs something, but it’s worth the savings in head banging.

Reply | Quote

We got it! One of our clever team sussed it out.
All you have to do is to change the target machine’s Regional Settings to English (United States), re-boot several times, install the package, change the Regional Settings back to English (Australian), re-boot several more times and heh presto – is don is good!

Now, at this point I could start a tirade about you-know-who thinking that American English is the only English in the world but you mightn’t understand 75% of the words so I think I will refrain myself.

Charlotte, your replies are a great encouragement and I don’t know how you make time to fit so many of us into your schedule. Thanks.

Reply | Quote

[indent]

---

American English is the only English in the world

---

[/indent]You mean it’s NOT?? Well what have all you benighted Antipodeans been speaking until you learned American?

Glad you found a solution … even if it is roundabout. If you’re going to do this regularly, I still suggest a 3rd party installer. It will definitely save wear and tear on your team’s nerves! And don’t blame it all on you-know-who. After all, the SQL standard uses US date format too.

Reply | Quote