From ngw Wed Jun 01 16:50:21 2005 From: "Joe Pampel" Date: Wed, 01 Jun 2005 16:50:21 +0000 To: ngw Subject: GW conflict with Excel 2k Message-Id: X-MARC-Message: https://marc.info/?l=ngw&m=119238043096962 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--=__Part0D2EDF5D.0__=" --=__Part0D2EDF5D.0__= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit We recently created a new corp image and rolled out a bunch of new workstations. One thing we did not test in QA was printing from excel, and well, now we have a bit of an issue! Apparently, if you install office 2k and then the groupwise client, some DLL somewhere is getting backrevved or something and bits of excel break. New spreadsheets are ok usually, but ones the user has created earlier (pre their new PC) still open but crash excel if they get edited "too much" or if there is an attempt to print or save changes. Did some googling but have not seen an ID on this issue. The fix (so far) is to install the GW client first, and then Office.. Anyone been through this before I spend the afternoon doing installs & file compares to see what gets whacked? Thx! - Joe --=__Part0D2EDF5D.0__= Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Description: HTML
We recently created a new corp image and rolled out a bunch of = new workstations. One thing we did not test in QA was printing from excel, = and well, now we have a bit of an issue!
Apparently, if you install office 2k and then the groupwise client, = some DLL somewhere is getting backrevved or something and bits of excel = break.  New spreadsheets are ok usually, but ones the user has = created earlier (pre their new PC) still open but crash excel if they get = edited "too much" or if there is an attempt to print or save changes. Did = some googling but have not seen an ID on this issue.
The fix (so far) is to install the GW client first, and then Office.. =  
Anyone been through this before I spend the afternoon doing installs = & file compares to see what gets whacked?
 
Thx! - Joe
--=__Part0D2EDF5D.0__=--