Re: PROBLEM: 12.1 version of Word 2008 will not open WinWord .doc

Bugs in 3rd party apps?
LOL
Docs created with MS Office on PC
Docs sent via Exchange server to Entourage/MS Webmail users.
Files fail to open with double-click.

Where's the third-party software, JE?
That's the best one yet.
Are you really Steve Balmer?

Your methods or best practices may work in some Bank of America
environment,
but not where I work.

Scott

On 5/20/08 7:15 AM 5/20/08, in article
jemcgimpsey-F8CA19.08150720052008@[EMAIL PROTECTED]
 "JE McGimpsey"
<jemcgimpsey@[EMAIL PROTECTED]
> wrote:

> In article <ee9b714.103@[EMAIL PROTECTED]
>,
>  Richard_Starling@[EMAIL PROTECTED]
 wrote:
> 
>> JE, do those same users have the issue of not being able to double
click an
>> email attachment? If, like me, they have to save the attachment then go
to
>> Word and then do a File/Open I'm sure they wouldn't 'get it'.
> 
> Of course they do.
> 
> After the initial confusion (where we got a half-dozen or so calls), we
> put out a message to the users reminding them to use File/Open, and we
> haven't had a complaint since. Can't be 100% positive that all the desks
> are updated yet, but the vast majority are.
> 
> FWIW, we also have regularly told them that they should, if they plan to
> work on a do***ent, save it first and work off the saved copy. That's
> far more stable than editing docs in a tem****ary directory, and just
> good practice.
> 
>> Everyone is assuming that MS have deprecated the WDBN file type, as
>> far as I know there's nothing in the release notes and I still say
>> that either MS did not test this properly or they have a blatant
>> disregard for the usability of their software on the Mac platform.
> 
> Or, as has been stated many times, they didn't realize that third-party
> applications were applying type codes that hasn't been applied by an MS
> app during this century, and which in 99% of cases is *incorrect*.
> 
> It's a BUG, but in the third-party apps!
> 
> And FWIW, the WDBN file type has been deprecated since Office 98 when
> the new type came out. Sup****t for deprecated features are often carried
> along by software developers for a version (or several), but in general,
> removal of sup****t for deprecated items is not typically announced in a
> release note.
> 
>> I have gone back to 12.0.1 and will not upgrade until
>> this is fixed.
> 
> Well, living with dozens of bugs may work for you, and that's fine. It
> doesn't for the users I sup****t.
> 
> They'd rather be more productive than petulant.