Hi Renoir,

I've had a problem on Win2K that looks very similar to what's described here but using Word2000 and Word97. If there is a network printer set as default BUT it is not available then either version of word appears to start up but fails with some exit-only type of error within the minute.

A real PITA in my opinion that MS could do something about. Certainly the kind of thing that I expect to see fixed in XP.

So, I'm not so sure that a product that is "old" is the real problem here. And I am not at all sure that one's "choice" of product level/version is always under developer control. Look at how often people here have said that they still have to support the FPD or FPW versions of their products because USERS are quite happy and have no inclination to "upgrade".

Regards,
Jim


>Lloyd,
>
>I think the comment you made that got all that going was, "I sure hope this issue is addressed in a Win2k compatibility update..." Ed knows that it won't be addressed for all the reasons he stated. Everything you do to resolve your issues will take some manipulation on your part. Ed makes an excellent point with his "Tank" analogy. If it's under your control try to have the platform and the software compatable or expect some possible unresolvable difficulties to arise.
>
>Renoir
>
>>Wow!
>>
>>Guess I touched a nerve there. We found a problem, asked for help, got some hints, solved the problem and reported some more info about the problem and solution to help other people who might be in a similar situation.
>>
>>You can't please everyone, oh well, thats life I guess. We are getting the whole system converted to VFP, but untill that time we still have a requirement for running FoxPro 2.6 and it seems so do other people, as there is a FoxPro 2.6 Category on here.
>>
>>Cheers anyway.