Patrick Hollermann
patrickh at parkindustries.com
Tue Apr 22 09:48:25 CDT 2003
Marty, Thank you for the response. I check out the links you provided and everything checked out ok. I then started digging into the configuration of the machines that worked and those that didn't. I came down to a VB file (Vbeext1.olb) on the development machine having a more current date than the machines not working. It was updated by a ftp terminal software we use to access some software. Thank you again for the suggestions. Patrick L. Hollermann -----Original Message----- From: MartyConnelly [mailto:martyconnelly at shaw.ca] Sent: Tuesday, April 15, 2003 4:12 PM To: accessd at databaseadvisors.com Subject: Re: [AccessD] Visual Basic 6 setup toolkit error with packagingwizard from Dev XP Patrick Hollermann wrote: > Hello List, > I have an error that is giving me fits. I have a package made using MS > development package wizard for XP and it has worked well for me for > the last year. I redistributed and access runtime package (FE) that > looks at a SQL (BE) within a confined office complex for 5 revisions. > This has worked fine, until now. The process of putting a package > together on a server on the network and getting access to it from the > users work station appears to work fine. We are running Office XP with > SP3 installed on all machines. We have a combination of windows 2000 > and NT workstations at the users desks. > > Here is the process I follow when installing on a users workstation. > As I run the install process it starts running, opens, looks for > available space, and on the NT workstations it then starts installing > the Access Runtime files and then the 6mb adp file. On some of the > 2000 workstations the install also runs with no trouble. On some of > the 2000 workstations I get the following error in a Visual Basic 6.0 > Setup Toolkit pop up dialog box: > > "The Office System Pack cannot be installed in this system because it > requires Windows NT4.0 Service Pack 6 or later". > > After this error the installation terminates and says unsuccessful. > Has anyone seen this error before? Any places to look on the > development machine for something that I might have changed that is > causing this problem? As always any help is welcome. Thank you all for > your help and or suggestions. > > P.S. management won't spring for a different packaging software like > Sage.. I asked& > > Patrick L. Hollermann > Park Industries, Inc. > St. Cloud MN, USA > It might be admin install rights on Win2000 or all the Win 2000 clients on same SP. http://www.microsoft.com/office/ork/xp/one/depa04.htm http://www.microsoft.com/office/ork/2000/journ/IntelliMirror.h _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com