Why?

[Jay R. Ashworth]

On Wed, Jun 30, 2004 at 06:19:49PM -0400, Kenneth Brody wrote:
> "Jay R. Ashworth" wrote:
> [...]
> > > > I don't want to upgrade to a newer version (unless it is going to provide
> > > > some feature a really want, like memo printing) an risk the chance of
> > > > something that is working fine now, breaking.
> > > [...]
> > >
> > > Then how do you expect your problem to be fixed?
> > 
> > Well, as I noted, sometimes you don't have a choice.
> > 
> > The *issue* is who's choice that's going to be.
> 
> Well, he's apparently decided to chose "I'm not upgrading for bugfixes".
> So, my question is, even if 5.0.13 explicitly listed his situation as
> having been fixed, would he even upgrade?  (His quote above seems to
> answer "no".)

Perhaps.  

> > If the *problem* is actually configuration, or O/S configuration, or
> > something else that is *not* a fixed bug on the release train from
> > $MY_RELEASE to current, and yet support won't talk to me, then what?
> 
> On the other hand, aside from saying "these 3 lines of code cause *report
> to crash", he hasn't talked to fpsupport at all.  (AFAIK)
> 
> For all I know, they'll say "send it to us even though you're not on the
> latest version, but if we can't duplicate it, you'll have to verify it
> yourself on the latest version before we can treat it as a bug".

Also perhaps.  But this doesn't actually speak to my problem in a
general way.

Cheers,
-- jra
-- 
Jay R. Ashworth                                                jra at baylink.com
Designer                          Baylink                             RFC 2100
Ashworth & Associates        The Things I Think                        '87 e24
St Petersburg FL USA      http://baylink.pitas.com             +1 727 647 1274

                2004 Stanley Cup Champion Tampa Bay Lightning