Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Printing from jaguar component

13 posts in General Discussion (old) Last posting was on 2000-02-16 15:04:42.0Z
Peter Reedijk Posted on 2000-02-14 15:38:52.0Z
Newsgroups: sybase.public.easerver
From: "Peter Reedijk" <peter.reedijk@pica.nl>
Organization: 192.87.44.228
X-Newsreader: AspNNTP 1.41 (Advent 2000, Inc.)
Subject: Printing from jaguar component
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Mon, 14 Feb 2000 10:38:52 -0500
Lines: 19
NNTP-Posting-Host: 207.156.232.4
Message-ID: <347_34brYGwd$GA.327@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28756
Article PK: 160872

The message below was posted more than half a year ago in this newsgroup.
Several fixes later, I've tried to implement PrintOpen() etc. Still returns -1,
so bug doesn't look fixed yet. Can anyone confirm this?

Furthermore, on Solaris datastore.Print() also doesn't work (returns -1). Is
that also a known bug?

TIA
Peter


(quote)
If you want to print a datawindow from PB/Jag component, currently you can use
<dw obj>.Print()

We have noticed that in a PB/Jag component if you use PrintOpen() and then
functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they fail
with -1 return code. A bug (cr 201828) has been opened against this problem. Not
ETA for fix....

HTH
(unquote)


Dave Wolf [Sybase] Posted on 2000-02-14 15:41:58.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Printing from jaguar component
Date: Mon, 14 Feb 2000 10:41:58 -0500
Lines: 41
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: 158.159.8.63
Message-ID: <347_6YRHFKwd$GA.332@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28753
Article PK: 154711

Peter,

These newsgroups are not a replacement for technical support. There is
absolutely no guarantee that a bug reported on these newsgroups will be
fixed. As you've noted, they rarely are. If youhave a bug please open a
technical support case so these things dont go unfixed for a year.

Dave Wolf
Internet Applications Division

Peter Reedijk <peter.reedijk@pica.nl> wrote in message
news:34brYGwd$GA.327@forums.sybase.com...
> The message below was posted more than half a year ago in this newsgroup.
> Several fixes later, I've tried to implement PrintOpen() etc. Still
returns -1,
> so bug doesn't look fixed yet. Can anyone confirm this?
>
> Furthermore, on Solaris datastore.Print() also doesn't work (returns -1).
Is
> that also a known bug?
>
> TIA
> Peter
>
>
> (quote)
> If you want to print a datawindow from PB/Jag component, currently you can
use
> <dw obj>.Print()
>
> We have noticed that in a PB/Jag component if you use PrintOpen() and then
> functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
fail
> with -1 return code. A bug (cr 201828) has been opened against this
problem. Not
> ETA for fix....
>
> HTH
> (unquote)


Peter Reedijk Posted on 2000-02-15 10:32:05.0Z
Newsgroups: sybase.public.easerver
From: "Peter Reedijk" <peter.reedijk@pica.nl>
Organization: 192.87.44.228
X-Newsreader: AspNNTP 1.41 (Advent 2000, Inc.)
Subject: Re: Printing from jaguar component
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Feb 2000 05:32:05 -0500
Lines: 46
NNTP-Posting-Host: 207.156.232.4
Message-ID: <347_csHPn$5d$GA.184@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28671
Article PK: 160799

Forgive me for getting back to this, but my experience is that it's very hard to
get information about the status of cases opened and therefore 'owned' by
someone else, so the best thing I know of, is asking here.
Are you suggesting that I should call support myself and open a case for
everything I consider a bug, even when it's obvious it has already been reported
by another programmer, somewhere in the world?

Peter

On Mon, 14 Feb 2000 10:41:58 -0500,
in powersoft.public.easerver

Dave Wolf [Sybase] <dwolf@sybase.com> wrote:
>Peter,
>
>These newsgroups are not a replacement for technical support. There is
>absolutely no guarantee that a bug reported on these newsgroups will be
>fixed. As you've noted, they rarely are. If youhave a bug please open a
>technical support case so these things dont go unfixed for a year.
>
>Dave Wolf
>Internet Applications Division
>
>Peter Reedijk <peter.reedijk@pica.nl> wrote in message
>news:34brYGwd$GA.327@forums.sybase.com...
>> The message below was posted more than half a year ago in this newsgroup.
>> Several fixes later, I've tried to implement PrintOpen() etc. Still
>returns -1,
>> so bug doesn't look fixed yet. Can anyone confirm this?
>>
>> Furthermore, on Solaris datastore.Print() also doesn't work (returns -1).
>Is
>> that also a known bug?
>>
>> TIA
>> Peter
>>
>>
>> (quote)
>> If you want to print a datawindow from PB/Jag component, currently you can
>use
>> <dw obj>.Print()
>>
>> We have noticed that in a PB/Jag component if you use PrintOpen() and then
>> functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
>fail
>> with -1 return code. A bug (cr 201828) has been opened against this
>problem. Not
>> ETA for fix....
>>
>> HTH
>> (unquote)
>
>


Bill Green[TeamSybase] Posted on 2000-02-15 15:56:14.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 15 Feb 2000 10:56:14 -0500
From: "Bill Green[TeamSybase]" <bill.green@teamsybase.com>
Reply-To: bill.green@teamsybase.com
Organization: TeamSybase
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Printing from jaguar component
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 87
NNTP-Posting-Host: threshold3.jpmorgan.com 169.71.1.12
Message-ID: <347_38A9771E.CECDC961@teamsybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_csHPn$5d$GA.184@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28651
Article PK: 160782

Despite the affirmations of the Sybase folks here, I would temper that just a
little. It *does* depend on the problem. If it is something you want fixed, then
report it. If someone else already has, your case will be linked to that case, but
then you have the ability to get follow-up. Additionally, if the problem is
important to you, it may not have been reported as important by someone else, and
therefore be lower in the processing queue than you might want it to be. If it's
something that you *know* has been reported by someone else, and you don't really
care if it gets fixed or not (because of a workaround, or whatever), then I would
say you will derive no benefit from reporting the issue.

Finally, and probably most important, it depends of the level of support you have
with Sybase. If you have custom support, I would absolutely report it no matter
what. If you use pay-as-you-go support, then obviously you need to make a judgment
call on whether it's important enough for you to spend money on.

One thing I would remind you of - It's never obvious that a bug has already been
reported by another programmer, even if it has been discussed here in a newsgroup
extensively. Which is why Evan reminded me that you should still report the bug even
if you get a suitable workaround.


HTH,
Bill

Peter Reedijk wrote:

> Forgive me for getting back to this, but my experience is that it's very hard to
> get information about the status of cases opened and therefore 'owned' by
> someone else, so the best thing I know of, is asking here.
> Are you suggesting that I should call support myself and open a case for
> everything I consider a bug, even when it's obvious it has already been reported
> by another programmer, somewhere in the world?
>
> Peter
>
> On Mon, 14 Feb 2000 10:41:58 -0500,
> in powersoft.public.easerver
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote:
> >Peter,
> >
> >These newsgroups are not a replacement for technical support. There is
> >absolutely no guarantee that a bug reported on these newsgroups will be
> >fixed. As you've noted, they rarely are. If youhave a bug please open a
> >technical support case so these things dont go unfixed for a year.
> >
> >Dave Wolf
> >Internet Applications Division
> >
> >Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> >news:34brYGwd$GA.327@forums.sybase.com...
> >> The message below was posted more than half a year ago in this newsgroup.
> >> Several fixes later, I've tried to implement PrintOpen() etc. Still
> >returns -1,
> >> so bug doesn't look fixed yet. Can anyone confirm this?
> >>
> >> Furthermore, on Solaris datastore.Print() also doesn't work (returns -1).
> >Is
> >> that also a known bug?
> >>
> >> TIA
> >> Peter
> >>
> >>
> >> (quote)
> >> If you want to print a datawindow from PB/Jag component, currently you can
> >use
> >> <dw obj>.Print()
> >>
> >> We have noticed that in a PB/Jag component if you use PrintOpen() and then
> >> functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
> >fail
> >> with -1 return code. A bug (cr 201828) has been opened against this
> >problem. Not
> >> ETA for fix....
> >>
> >> HTH
> >> (unquote)
> >
> >

--
Bill Green[TeamSybase]

Good Links to know:
Sybase Developer Network (SDN) - http://www.sybase.com/sdn
PFC Guide - http://www.pfcguide.com
Power3 - Custom Training - http://www.power3.com


Dave Wolf [Sybase] Posted on 2000-02-15 15:20:03.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Printing from jaguar component
Date: Tue, 15 Feb 2000 10:20:03 -0500
Lines: 69
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: dwolf-nt.sybase.com 157.133.40.74
Message-ID: <347_MVbPfi8d$GA.184@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_csHPn$5d$GA.184@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28655
Article PK: 160786

In short, yes. Feel free to ask here as a first try, but support is the
proper official channel.

Dave Wolf
Internet Applications Division

Peter Reedijk <peter.reedijk@pica.nl> wrote in message
news:csHPn$5d$GA.184@forums.sybase.com...
> Forgive me for getting back to this, but my experience is that it's very
hard to
> get information about the status of cases opened and therefore 'owned' by
> someone else, so the best thing I know of, is asking here.
> Are you suggesting that I should call support myself and open a case for
> everything I consider a bug, even when it's obvious it has already been
reported
> by another programmer, somewhere in the world?
>
> Peter
>
> On Mon, 14 Feb 2000 10:41:58 -0500,
> in powersoft.public.easerver
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote:
> >Peter,
> >
> >These newsgroups are not a replacement for technical support. There is
> >absolutely no guarantee that a bug reported on these newsgroups will be
> >fixed. As you've noted, they rarely are. If youhave a bug please open a
> >technical support case so these things dont go unfixed for a year.
> >
> >Dave Wolf
> >Internet Applications Division
> >
> >Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> >news:34brYGwd$GA.327@forums.sybase.com...
> >> The message below was posted more than half a year ago in this
newsgroup.
> >> Several fixes later, I've tried to implement PrintOpen() etc. Still
> >returns -1,
> >> so bug doesn't look fixed yet. Can anyone confirm this?
> >>
> >> Furthermore, on Solaris datastore.Print() also doesn't work
(returns -1).
> >Is
> >> that also a known bug?
> >>
> >> TIA
> >> Peter
> >>
> >>
> >> (quote)
> >> If you want to print a datawindow from PB/Jag component, currently you
can
> >use
> >> <dw obj>.Print()
> >>
> >> We have noticed that in a PB/Jag component if you use PrintOpen() and
then
> >> functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
> >fail
> >> with -1 return code. A bug (cr 201828) has been opened against this
> >problem. Not
> >> ETA for fix....
> >>
> >> HTH
> >> (unquote)
> >
> >


Lance Andersen Posted on 2000-02-15 12:16:39.0Z
Newsgroups: sybase.public.easerver
Date: Tue, 15 Feb 2000 07:16:39 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Printing from jaguar component
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 67
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38A943A7.1F7D4B57@sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_csHPn$5d$GA.184@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28667
Article PK: 160797

If you need a fix, the answer to your question is yes. One of the ways
that we prioritize our fixes is based on the number of customer
cases associated to the bug. If you do not need an urgent fix, you
should be able to track bug status via my.sybase.com I believe.


Lance

Peter Reedijk wrote:
>
> Forgive me for getting back to this, but my experience is that it's very hard to
> get information about the status of cases opened and therefore 'owned' by
> someone else, so the best thing I know of, is asking here.
> Are you suggesting that I should call support myself and open a case for
> everything I consider a bug, even when it's obvious it has already been reported
> by another programmer, somewhere in the world?
>
> Peter
>
> On Mon, 14 Feb 2000 10:41:58 -0500,
> in powersoft.public.easerver
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote:
> >Peter,
> >
> >These newsgroups are not a replacement for technical support. There is
> >absolutely no guarantee that a bug reported on these newsgroups will be
> >fixed. As you've noted, they rarely are. If youhave a bug please open a
> >technical support case so these things dont go unfixed for a year.
> >
> >Dave Wolf
> >Internet Applications Division
> >
> >Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> >news:34brYGwd$GA.327@forums.sybase.com...
> >> The message below was posted more than half a year ago in this newsgroup.
> >> Several fixes later, I've tried to implement PrintOpen() etc. Still
> >returns -1,
> >> so bug doesn't look fixed yet. Can anyone confirm this?
> >>
> >> Furthermore, on Solaris datastore.Print() also doesn't work (returns -1).
> >Is
> >> that also a known bug?
> >>
> >> TIA
> >> Peter
> >>
> >>
> >> (quote)
> >> If you want to print a datawindow from PB/Jag component, currently you can
> >use
> >> <dw obj>.Print()
> >>
> >> We have noticed that in a PB/Jag component if you use PrintOpen() and then
> >> functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
> >fail
> >> with -1 return code. A bug (cr 201828) has been opened against this
> >problem. Not
> >> ETA for fix....
> >>
> >> HTH
> >> (unquote)
> >
> >

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================


<=one way=> Posted on 2000-02-14 15:58:56.0Z
Newsgroups: sybase.public.easerver
From: "<=one way=>" <oneway_111@yahoo.com>
Subject: Re: Printing from jaguar component
Date: Mon, 14 Feb 2000 10:58:56 -0500
Lines: 52
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host: oppenheimer163.oppenheimerfunds.com 216.44.5.163
Message-ID: <347_McVEpVwd$GA.149@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28751
Article PK: 160871

Isn't Sybase interested in fixing bugs? And if yes, why not fix issues that
were confirmed in a newsgroup as a bug?

Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
news:6YRHFKwd$GA.332@forums.sybase.com...
> Peter,
>
> These newsgroups are not a replacement for technical support. There is
> absolutely no guarantee that a bug reported on these newsgroups will be
> fixed. As you've noted, they rarely are. If youhave a bug please open a
> technical support case so these things dont go unfixed for a year.
>
> Dave Wolf
> Internet Applications Division
>
> Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> news:34brYGwd$GA.327@forums.sybase.com...
> > The message below was posted more than half a year ago in this
newsgroup.
> > Several fixes later, I've tried to implement PrintOpen() etc. Still
> returns -1,
> > so bug doesn't look fixed yet. Can anyone confirm this?
> >
> > Furthermore, on Solaris datastore.Print() also doesn't work
(returns -1).
> Is
> > that also a known bug?
> >
> > TIA
> > Peter
> >
> >
> > (quote)
> > If you want to print a datawindow from PB/Jag component, currently you
can
> use
> > <dw obj>.Print()
> >
> > We have noticed that in a PB/Jag component if you use PrintOpen() and
then
> > functions such as PrintDataWindow(), PrintText(), PrintLine() etc, they
> fail
> > with -1 return code. A bug (cr 201828) has been opened against this
> problem. Not
> > ETA for fix....
> >
> > HTH
> > (unquote)
>
>


Dave Wolf [Sybase] Posted on 2000-02-14 16:09:12.0Z
Newsgroups: sybase.public.easerver
From: "Dave Wolf [Sybase]" <dwolf@sybase.com>
Subject: Re: Printing from jaguar component
Date: Mon, 14 Feb 2000 11:09:12 -0500
Lines: 75
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
NNTP-Posting-Host: 158.159.8.63
Message-ID: <347_eyR5SZwd$GA.332@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28749
Article PK: 160869

Yes we are very interested in fixing bugs. As a matter of fact, I have
opened numerous cases from things Ive seen in the newsgroups. My point is
that there is no GUARANTEE that we will always see a bug, have a
reproduceable, etc etc when it comes in on the newgroups. There is no
guanteed quality of service from the newsgroups. The Sybase staff who
answer here do so in a strictly volunteer fashion. Answering questions here
is not a part of my job. I do it as a service to the Jag community. As Im
sure you can imagine, to open a bug and be sure we fix the right bug, we
need a full desription, a full reproduceable, and someone to confirm we did
indeed fix it. Newsgroups arent condusive to this level of support.
Technical support is the proper forum. We definately want bugs fixedm thats
why I definately want the point made support is the right way to do this.

Dave Wolf
Internet Applications Division

<=one way=> <oneway_111@yahoo.com> wrote in message
news:McVEpVwd$GA.149@forums.sybase.com...
> Isn't Sybase interested in fixing bugs? And if yes, why not fix issues
that
> were confirmed in a newsgroup as a bug?
>
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> news:6YRHFKwd$GA.332@forums.sybase.com...
> > Peter,
> >
> > These newsgroups are not a replacement for technical support. There is
> > absolutely no guarantee that a bug reported on these newsgroups will be
> > fixed. As you've noted, they rarely are. If youhave a bug please open
a
> > technical support case so these things dont go unfixed for a year.
> >
> > Dave Wolf
> > Internet Applications Division
> >
> > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> > news:34brYGwd$GA.327@forums.sybase.com...
> > > The message below was posted more than half a year ago in this
> newsgroup.
> > > Several fixes later, I've tried to implement PrintOpen() etc. Still
> > returns -1,
> > > so bug doesn't look fixed yet. Can anyone confirm this?
> > >
> > > Furthermore, on Solaris datastore.Print() also doesn't work
> (returns -1).
> > Is
> > > that also a known bug?
> > >
> > > TIA
> > > Peter
> > >
> > >
> > > (quote)
> > > If you want to print a datawindow from PB/Jag component, currently you
> can
> > use
> > > <dw obj>.Print()
> > >
> > > We have noticed that in a PB/Jag component if you use PrintOpen() and
> then
> > > functions such as PrintDataWindow(), PrintText(), PrintLine() etc,
they
> > fail
> > > with -1 return code. A bug (cr 201828) has been opened against this
> > problem. Not
> > > ETA for fix....
> > >
> > > HTH
> > > (unquote)
> >
> >
>
>


<=one way=> Posted on 2000-02-14 16:47:13.0Z
Newsgroups: sybase.public.easerver
From: "<=one way=>" <oneway_111@yahoo.com>
Subject: Re: Printing from jaguar component
Date: Mon, 14 Feb 2000 11:47:13 -0500
Lines: 97
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
NNTP-Posting-Host: oppenheimer163.oppenheimerfunds.com 216.44.5.163
Message-ID: <347_Caypowwd$GA.149@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com> <347_eyR5SZwd$GA.332@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28745
Article PK: 160867

1. First of all, thank you for your support of this newsgroup. You are doing
a great job. I doubt using of EAS would realistically be possible without
this group.

2. I do not think it should matter much how a case is opened. If someone
does not have a support contract but raises a serious issue, does it mean
that the issue can be ignored? Probably not, if the company wants people to
use its product. Maybe Sybase should rethink its policy in this regard.

Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
news:eyR5SZwd$GA.332@forums.sybase.com...
> Yes we are very interested in fixing bugs. As a matter of fact, I have
> opened numerous cases from things Ive seen in the newsgroups. My point is
> that there is no GUARANTEE that we will always see a bug, have a
> reproduceable, etc etc when it comes in on the newgroups. There is no
> guanteed quality of service from the newsgroups. The Sybase staff who
> answer here do so in a strictly volunteer fashion. Answering questions
here
> is not a part of my job. I do it as a service to the Jag community. As
Im
> sure you can imagine, to open a bug and be sure we fix the right bug, we
> need a full desription, a full reproduceable, and someone to confirm we
did
> indeed fix it. Newsgroups arent condusive to this level of support.
> Technical support is the proper forum. We definately want bugs fixedm
thats
> why I definately want the point made support is the right way to do this.
>
> Dave Wolf
> Internet Applications Division
>
> <=one way=> <oneway_111@yahoo.com> wrote in message
> news:McVEpVwd$GA.149@forums.sybase.com...
> > Isn't Sybase interested in fixing bugs? And if yes, why not fix issues
> that
> > were confirmed in a newsgroup as a bug?
> >
> > Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> > news:6YRHFKwd$GA.332@forums.sybase.com...
> > > Peter,
> > >
> > > These newsgroups are not a replacement for technical support. There
is
> > > absolutely no guarantee that a bug reported on these newsgroups will
be
> > > fixed. As you've noted, they rarely are. If youhave a bug please
open
> a
> > > technical support case so these things dont go unfixed for a year.
> > >
> > > Dave Wolf
> > > Internet Applications Division
> > >
> > > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> > > news:34brYGwd$GA.327@forums.sybase.com...
> > > > The message below was posted more than half a year ago in this
> > newsgroup.
> > > > Several fixes later, I've tried to implement PrintOpen() etc. Still
> > > returns -1,
> > > > so bug doesn't look fixed yet. Can anyone confirm this?
> > > >
> > > > Furthermore, on Solaris datastore.Print() also doesn't work
> > (returns -1).
> > > Is
> > > > that also a known bug?
> > > >
> > > > TIA
> > > > Peter
> > > >
> > > >
> > > > (quote)
> > > > If you want to print a datawindow from PB/Jag component, currently
you
> > can
> > > use
> > > > <dw obj>.Print()
> > > >
> > > > We have noticed that in a PB/Jag component if you use PrintOpen()
and
> > then
> > > > functions such as PrintDataWindow(), PrintText(), PrintLine() etc,
> they
> > > fail
> > > > with -1 return code. A bug (cr 201828) has been opened against this
> > > problem. Not
> > > > ETA for fix....
> > > >
> > > > HTH
> > > > (unquote)
> > >
> > >
> >
> >
>
>


Bill Green[TeamSybase] Posted on 2000-02-14 20:02:03.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 14 Feb 2000 15:02:03 -0500
From: "Bill Green[TeamSybase]" <bill.green@teamsybase.com>
Reply-To: bill.green@teamsybase.com
Organization: TeamSybase
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Printing from jaguar component
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 136
NNTP-Posting-Host: threshold3.jpmorgan.com 169.71.1.12
Message-ID: <347_38A85F3A.2189A472@teamsybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com> <347_eyR5SZwd$GA.332@forums.sybase.com> <347_Caypowwd$GA.149@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28724
Article PK: 160848

I'm afraid I would argue your second point a little. (Absolutely no argument
with the first). If you were a software vendor, and you had lets say (to keep it
simple) 1 person doing support. Now a big corporate customer who buys 100's of
copies of your software, and has a mega-bucks support contract calls with a
problem. Around the same time, Joe Schmoe (me) calls you with a problem I'm
having with my 1 license and pay-as-you-go support. And then someone opens a
case via your internet support site. At the same time, 2 people on your
newsgroup post messages about issues they have. How do you direct your tech
support focus? Now, multiply those numbers by 400,000+ licenses (probably
exceeding 500,000 by this point), and you're facing a daunting task. Therefore,
you make some choices - Fix the most essential bugs, help the paying customers,
(becuase you have to track and report on those), and, if time permits, tackle
the other reported issues from non-revenue based reporting sources. You
certainly can't spend time and resources tracking and monitoring status of
issues that may be raised in these newsgroups.

I wish it could be different but the fact is there's only a certian number of
resources available for all your products, and you have to establish channels
that allow you to maintain some semblance of control. That's why you use these
forums to discuss issues, ask questions and benefit from the expertise and
effort of the Dave's and Carson's of the world. If it's a bug, however, you have
to try to use the channel that will give you the best result.

Just my opinion though,

Bill

"<=one way=>" wrote:

> 1. First of all, thank you for your support of this newsgroup. You are doing
> a great job. I doubt using of EAS would realistically be possible without
> this group.
>
> 2. I do not think it should matter much how a case is opened. If someone
> does not have a support contract but raises a serious issue, does it mean
> that the issue can be ignored? Probably not, if the company wants people to
> use its product. Maybe Sybase should rethink its policy in this regard.
>
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> news:eyR5SZwd$GA.332@forums.sybase.com...
> > Yes we are very interested in fixing bugs. As a matter of fact, I have
> > opened numerous cases from things Ive seen in the newsgroups. My point is
> > that there is no GUARANTEE that we will always see a bug, have a
> > reproduceable, etc etc when it comes in on the newgroups. There is no
> > guanteed quality of service from the newsgroups. The Sybase staff who
> > answer here do so in a strictly volunteer fashion. Answering questions
> here
> > is not a part of my job. I do it as a service to the Jag community. As
> Im
> > sure you can imagine, to open a bug and be sure we fix the right bug, we
> > need a full desription, a full reproduceable, and someone to confirm we
> did
> > indeed fix it. Newsgroups arent condusive to this level of support.
> > Technical support is the proper forum. We definately want bugs fixedm
> thats
> > why I definately want the point made support is the right way to do this.
> >
> > Dave Wolf
> > Internet Applications Division
> >
> > <=one way=> <oneway_111@yahoo.com> wrote in message
> > news:McVEpVwd$GA.149@forums.sybase.com...
> > > Isn't Sybase interested in fixing bugs? And if yes, why not fix issues
> > that
> > > were confirmed in a newsgroup as a bug?
> > >
> > > Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> > > news:6YRHFKwd$GA.332@forums.sybase.com...
> > > > Peter,
> > > >
> > > > These newsgroups are not a replacement for technical support. There
> is
> > > > absolutely no guarantee that a bug reported on these newsgroups will
> be
> > > > fixed. As you've noted, they rarely are. If youhave a bug please
> open
> > a
> > > > technical support case so these things dont go unfixed for a year.
> > > >
> > > > Dave Wolf
> > > > Internet Applications Division
> > > >
> > > > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> > > > news:34brYGwd$GA.327@forums.sybase.com...
> > > > > The message below was posted more than half a year ago in this
> > > newsgroup.
> > > > > Several fixes later, I've tried to implement PrintOpen() etc. Still
> > > > returns -1,
> > > > > so bug doesn't look fixed yet. Can anyone confirm this?
> > > > >
> > > > > Furthermore, on Solaris datastore.Print() also doesn't work
> > > (returns -1).
> > > > Is
> > > > > that also a known bug?
> > > > >
> > > > > TIA
> > > > > Peter
> > > > >
> > > > >
> > > > > (quote)
> > > > > If you want to print a datawindow from PB/Jag component, currently
> you
> > > can
> > > > use
> > > > > <dw obj>.Print()
> > > > >
> > > > > We have noticed that in a PB/Jag component if you use PrintOpen()
> and
> > > then
> > > > > functions such as PrintDataWindow(), PrintText(), PrintLine() etc,
> > they
> > > > fail
> > > > > with -1 return code. A bug (cr 201828) has been opened against this
> > > > problem. Not
> > > > > ETA for fix....
> > > > >
> > > > > HTH
> > > > > (unquote)
> > > >
> > > >
> > >
> > >
> >
> >

--
Bill Green[TeamSybase]

Good Links to know:
Sybase Developer Network (SDN) - http://www.sybase.com/sdn
PFC Guide - http://www.pfcguide.com
Power3 - Custom Training - http://www.power3.com


Ken Hudson Posted on 2000-02-16 02:15:21.0Z
Newsgroups: sybase.public.easerver
From: "Ken Hudson" <ken@khudson.com>
Subject: Re: Printing from jaguar component
Date: Tue, 15 Feb 2000 18:15:21 -0800
Lines: 177
X-Newsreader: Microsoft Outlook Express 4.72.2106.4
X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4
NNTP-Posting-Host: ny-tc-ppp77.monmouth.com 209.191.41.78
Message-ID: <347_nTr4m9Ae$GA.149@forums.sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com> <347_eyR5SZwd$GA.332@forums.sybase.com> <347_Caypowwd$GA.149@forums.sybase.com> <347_38A85F3A.2189A472@teamsybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28612
Article PK: 160748

Here,Here......

Bill, I couldn't agree with you more. Fortunately, I work for what I hope
Sybase considers a corporate client. We are paying over and above the cost
of their product, $30000 for an annual tech support contract. And still, I
feel like much of the time, my staff(which consist of some very expensive NY
consultants) are having to debug this tool for Sybase.

To be perfectly frank, I feel I get better support from this newsgroup with
Dave and Carsons help than I get from the above tech support contract.

IMHO
Ken

Bill Green[TeamSybase] wrote in message
<38A85F3A.2189A472@teamsybase.com>...
>I'm afraid I would argue your second point a little. (Absolutely no
argument
>with the first). If you were a software vendor, and you had lets say (to
keep it
>simple) 1 person doing support. Now a big corporate customer who buys 100's
of
>copies of your software, and has a mega-bucks support contract calls with a
>problem. Around the same time, Joe Schmoe (me) calls you with a problem I'm
>having with my 1 license and pay-as-you-go support. And then someone opens
a
>case via your internet support site. At the same time, 2 people on your
>newsgroup post messages about issues they have. How do you direct your tech
>support focus? Now, multiply those numbers by 400,000+ licenses (probably
>exceeding 500,000 by this point), and you're facing a daunting task.
Therefore,
>you make some choices - Fix the most essential bugs, help the paying
customers,
>(becuase you have to track and report on those), and, if time permits,
tackle
>the other reported issues from non-revenue based reporting sources. You
>certainly can't spend time and resources tracking and monitoring status of
>issues that may be raised in these newsgroups.
>
>I wish it could be different but the fact is there's only a certian number
of
>resources available for all your products, and you have to establish
channels
>that allow you to maintain some semblance of control. That's why you use
these
>forums to discuss issues, ask questions and benefit from the expertise and
>effort of the Dave's and Carson's of the world. If it's a bug, however, you
have
>to try to use the channel that will give you the best result.
>
>Just my opinion though,
>
>Bill
>
>
>
>"<=one way=>" wrote:
>
>> 1. First of all, thank you for your support of this newsgroup. You are
doing
>> a great job. I doubt using of EAS would realistically be possible without
>> this group.
>>
>> 2. I do not think it should matter much how a case is opened. If someone
>> does not have a support contract but raises a serious issue, does it mean
>> that the issue can be ignored? Probably not, if the company wants people
to
>> use its product. Maybe Sybase should rethink its policy in this regard.
>>
>> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
>> news:eyR5SZwd$GA.332@forums.sybase.com...
>> > Yes we are very interested in fixing bugs. As a matter of fact, I have
>> > opened numerous cases from things Ive seen in the newsgroups. My point
is
>> > that there is no GUARANTEE that we will always see a bug, have a
>> > reproduceable, etc etc when it comes in on the newgroups. There is no
>> > guanteed quality of service from the newsgroups. The Sybase staff who
>> > answer here do so in a strictly volunteer fashion. Answering questions
>> here
>> > is not a part of my job. I do it as a service to the Jag community.
As
>> Im
>> > sure you can imagine, to open a bug and be sure we fix the right bug,
we
>> > need a full desription, a full reproduceable, and someone to confirm we
>> did
>> > indeed fix it. Newsgroups arent condusive to this level of support.
>> > Technical support is the proper forum. We definately want bugs fixedm
>> thats
>> > why I definately want the point made support is the right way to do
this.
>> >
>> > Dave Wolf
>> > Internet Applications Division
>> >
>> > <=one way=> <oneway_111@yahoo.com> wrote in message
>> > news:McVEpVwd$GA.149@forums.sybase.com...
>> > > Isn't Sybase interested in fixing bugs? And if yes, why not fix
issues
>> > that
>> > > were confirmed in a newsgroup as a bug?
>> > >
>> > > Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
>> > > news:6YRHFKwd$GA.332@forums.sybase.com...
>> > > > Peter,
>> > > >
>> > > > These newsgroups are not a replacement for technical support.
There
>> is
>> > > > absolutely no guarantee that a bug reported on these newsgroups
will
>> be
>> > > > fixed. As you've noted, they rarely are. If youhave a bug please
>> open
>> > a
>> > > > technical support case so these things dont go unfixed for a year.
>> > > >
>> > > > Dave Wolf
>> > > > Internet Applications Division
>> > > >
>> > > > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
>> > > > news:34brYGwd$GA.327@forums.sybase.com...
>> > > > > The message below was posted more than half a year ago in this
>> > > newsgroup.
>> > > > > Several fixes later, I've tried to implement PrintOpen() etc.
Still
>> > > > returns -1,
>> > > > > so bug doesn't look fixed yet. Can anyone confirm this?
>> > > > >
>> > > > > Furthermore, on Solaris datastore.Print() also doesn't work
>> > > (returns -1).
>> > > > Is
>> > > > > that also a known bug?
>> > > > >
>> > > > > TIA
>> > > > > Peter
>> > > > >
>> > > > >
>> > > > > (quote)
>> > > > > If you want to print a datawindow from PB/Jag component,
currently
>> you
>> > > can
>> > > > use
>> > > > > <dw obj>.Print()
>> > > > >
>> > > > > We have noticed that in a PB/Jag component if you use PrintOpen()
>> and
>> > > then
>> > > > > functions such as PrintDataWindow(), PrintText(), PrintLine()
etc,
>> > they
>> > > > fail
>> > > > > with -1 return code. A bug (cr 201828) has been opened against
this
>> > > > problem. Not
>> > > > > ETA for fix....
>> > > > >
>> > > > > HTH
>> > > > > (unquote)
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>
>--
>Bill Green[TeamSybase]
>
>Good Links to know:
>Sybase Developer Network (SDN) - http://www.sybase.com/sdn
>PFC Guide - http://www.pfcguide.com
>Power3 - Custom Training - http://www.power3.com
>
>


Bill Green[TeamSybase] Posted on 2000-02-16 15:04:42.0Z
Newsgroups: sybase.public.easerver
Date: Wed, 16 Feb 2000 10:04:42 -0500
From: "Bill Green[TeamSybase]" <bill.green@teamsybase.com>
Reply-To: bill.green@teamsybase.com
Organization: TeamSybase
X-Mailer: Mozilla 4.6 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Printing from jaguar component
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 192
NNTP-Posting-Host: threshold3.jpmorgan.com 169.71.1.12
Message-ID: <347_38AABC8A.FFDD7E3E@teamsybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com> <347_eyR5SZwd$GA.332@forums.sybase.com> <347_Caypowwd$GA.149@forums.sybase.com> <347_38A85F3A.2189A472@teamsybase.com> <347_nTr4m9Ae$GA.149@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28577
Article PK: 160719

I have had some good and bad experiences with custom support, but the fact
remains if I log a case through it, not only can I track the issue, I can
request regular status reports, prioritize what I want worked on etc etc. And
one thing you have to remember - There isn't a support organization in the world
that would have a Dave or Carson level person working their tech support lines.
Would you take your absolute best consultant right now and put them on your
help-desk?

So, while these forums are, and will continue to be the best avenue to ask a
technical question and hear from the experts, the fact remains if your question
reveals a deficiency in the product in any way, the only way it will ever get
worked on is if it's called in through the proper channels.

BTW, wanna hire an expensive not-NY consultant? <G>


Bill

Ken Hudson wrote:

> Here,Here......
>
> Bill, I couldn't agree with you more. Fortunately, I work for what I hope
> Sybase considers a corporate client. We are paying over and above the cost
> of their product, $30000 for an annual tech support contract. And still, I
> feel like much of the time, my staff(which consist of some very expensive NY
> consultants) are having to debug this tool for Sybase.
>
> To be perfectly frank, I feel I get better support from this newsgroup with
> Dave and Carsons help than I get from the above tech support contract.
>
> IMHO
> Ken
> Bill Green[TeamSybase] wrote in message
> <38A85F3A.2189A472@teamsybase.com>...
> >I'm afraid I would argue your second point a little. (Absolutely no
> argument
> >with the first). If you were a software vendor, and you had lets say (to
> keep it
> >simple) 1 person doing support. Now a big corporate customer who buys 100's
> of
> >copies of your software, and has a mega-bucks support contract calls with a
> >problem. Around the same time, Joe Schmoe (me) calls you with a problem I'm
> >having with my 1 license and pay-as-you-go support. And then someone opens
> a
> >case via your internet support site. At the same time, 2 people on your
> >newsgroup post messages about issues they have. How do you direct your tech
> >support focus? Now, multiply those numbers by 400,000+ licenses (probably
> >exceeding 500,000 by this point), and you're facing a daunting task.
> Therefore,
> >you make some choices - Fix the most essential bugs, help the paying
> customers,
> >(becuase you have to track and report on those), and, if time permits,
> tackle
> >the other reported issues from non-revenue based reporting sources. You
> >certainly can't spend time and resources tracking and monitoring status of
> >issues that may be raised in these newsgroups.
> >
> >I wish it could be different but the fact is there's only a certian number
> of
> >resources available for all your products, and you have to establish
> channels
> >that allow you to maintain some semblance of control. That's why you use
> these
> >forums to discuss issues, ask questions and benefit from the expertise and
> >effort of the Dave's and Carson's of the world. If it's a bug, however, you
> have
> >to try to use the channel that will give you the best result.
> >
> >Just my opinion though,
> >
> >Bill
> >
> >
> >
> >"<=one way=>" wrote:
> >
> >> 1. First of all, thank you for your support of this newsgroup. You are
> doing
> >> a great job. I doubt using of EAS would realistically be possible without
> >> this group.
> >>
> >> 2. I do not think it should matter much how a case is opened. If someone
> >> does not have a support contract but raises a serious issue, does it mean
> >> that the issue can be ignored? Probably not, if the company wants people
> to
> >> use its product. Maybe Sybase should rethink its policy in this regard.
> >>
> >> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> >> news:eyR5SZwd$GA.332@forums.sybase.com...
> >> > Yes we are very interested in fixing bugs. As a matter of fact, I have
> >> > opened numerous cases from things Ive seen in the newsgroups. My point
> is
> >> > that there is no GUARANTEE that we will always see a bug, have a
> >> > reproduceable, etc etc when it comes in on the newgroups. There is no
> >> > guanteed quality of service from the newsgroups. The Sybase staff who
> >> > answer here do so in a strictly volunteer fashion. Answering questions
> >> here
> >> > is not a part of my job. I do it as a service to the Jag community.
> As
> >> Im
> >> > sure you can imagine, to open a bug and be sure we fix the right bug,
> we
> >> > need a full desription, a full reproduceable, and someone to confirm we
> >> did
> >> > indeed fix it. Newsgroups arent condusive to this level of support.
> >> > Technical support is the proper forum. We definately want bugs fixedm
> >> thats
> >> > why I definately want the point made support is the right way to do
> this.
> >> >
> >> > Dave Wolf
> >> > Internet Applications Division
> >> >
> >> > <=one way=> <oneway_111@yahoo.com> wrote in message
> >> > news:McVEpVwd$GA.149@forums.sybase.com...
> >> > > Isn't Sybase interested in fixing bugs? And if yes, why not fix
> issues
> >> > that
> >> > > were confirmed in a newsgroup as a bug?
> >> > >
> >> > > Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> >> > > news:6YRHFKwd$GA.332@forums.sybase.com...
> >> > > > Peter,
> >> > > >
> >> > > > These newsgroups are not a replacement for technical support.
> There
> >> is
> >> > > > absolutely no guarantee that a bug reported on these newsgroups
> will
> >> be
> >> > > > fixed. As you've noted, they rarely are. If youhave a bug please
> >> open
> >> > a
> >> > > > technical support case so these things dont go unfixed for a year.
> >> > > >
> >> > > > Dave Wolf
> >> > > > Internet Applications Division
> >> > > >
> >> > > > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> >> > > > news:34brYGwd$GA.327@forums.sybase.com...
> >> > > > > The message below was posted more than half a year ago in this
> >> > > newsgroup.
> >> > > > > Several fixes later, I've tried to implement PrintOpen() etc.
> Still
> >> > > > returns -1,
> >> > > > > so bug doesn't look fixed yet. Can anyone confirm this?
> >> > > > >
> >> > > > > Furthermore, on Solaris datastore.Print() also doesn't work
> >> > > (returns -1).
> >> > > > Is
> >> > > > > that also a known bug?
> >> > > > >
> >> > > > > TIA
> >> > > > > Peter
> >> > > > >
> >> > > > >
> >> > > > > (quote)
> >> > > > > If you want to print a datawindow from PB/Jag component,
> currently
> >> you
> >> > > can
> >> > > > use
> >> > > > > <dw obj>.Print()
> >> > > > >
> >> > > > > We have noticed that in a PB/Jag component if you use PrintOpen()
> >> and
> >> > > then
> >> > > > > functions such as PrintDataWindow(), PrintText(), PrintLine()
> etc,
> >> > they
> >> > > > fail
> >> > > > > with -1 return code. A bug (cr 201828) has been opened against
> this
> >> > > > problem. Not
> >> > > > > ETA for fix....
> >> > > > >
> >> > > > > HTH
> >> > > > > (unquote)
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >
> >--
> >Bill Green[TeamSybase]
> >
> >Good Links to know:
> >Sybase Developer Network (SDN) - http://www.sybase.com/sdn
> >PFC Guide - http://www.pfcguide.com
> >Power3 - Custom Training - http://www.power3.com
> >
> >

--
Bill Green[TeamSybase]

Good Links to know:
Sybase Developer Network (SDN) - http://www.sybase.com/sdn
PFC Guide - http://www.pfcguide.com
Power3 - Custom Training - http://www.power3.com


Lance Andersen Posted on 2000-02-14 18:33:42.0Z
Newsgroups: sybase.public.easerver
Date: Mon, 14 Feb 2000 13:33:42 -0500
From: Lance Andersen <lancea@sybase.com>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Printing from jaguar component
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Lines: 115
NNTP-Posting-Host: alder.sybase.com 157.133.125.15
Message-ID: <347_38A84A86.55CC1AD7@sybase.com>
References: <347_34brYGwd$GA.327@forums.sybase.com> <347_6YRHFKwd$GA.332@forums.sybase.com> <347_McVEpVwd$GA.149@forums.sybase.com> <347_eyR5SZwd$GA.332@forums.sybase.com> <347_Caypowwd$GA.149@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.easerver:28735
Article PK: 160858

We do make a level of effort to deal with issues that
come in via the newsgroup. However, please realize (and maybe we
should post the welcome letter occassionally) that in order to guarantee
that you get a fix to an urgent issue, it is best to work with Tech
Support. The volume of questions in the newsgroups at times is
overwhelming and that is why we prefer to have issues brought
through the proper Tech Support channels.

Again, this does not mean that we will not log a bug, but it can
be more timely if you do it via Tech Support.

Regards,
Lance

"<=one way=>" wrote:
>
> 1. First of all, thank you for your support of this newsgroup. You are doing
> a great job. I doubt using of EAS would realistically be possible without
> this group.
>
> 2. I do not think it should matter much how a case is opened. If someone
> does not have a support contract but raises a serious issue, does it mean
> that the issue can be ignored? Probably not, if the company wants people to
> use its product. Maybe Sybase should rethink its policy in this regard.
>
> Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> news:eyR5SZwd$GA.332@forums.sybase.com...
> > Yes we are very interested in fixing bugs. As a matter of fact, I have
> > opened numerous cases from things Ive seen in the newsgroups. My point is
> > that there is no GUARANTEE that we will always see a bug, have a
> > reproduceable, etc etc when it comes in on the newgroups. There is no
> > guanteed quality of service from the newsgroups. The Sybase staff who
> > answer here do so in a strictly volunteer fashion. Answering questions
> here
> > is not a part of my job. I do it as a service to the Jag community. As
> Im
> > sure you can imagine, to open a bug and be sure we fix the right bug, we
> > need a full desription, a full reproduceable, and someone to confirm we
> did
> > indeed fix it. Newsgroups arent condusive to this level of support.
> > Technical support is the proper forum. We definately want bugs fixedm
> thats
> > why I definately want the point made support is the right way to do this.
> >
> > Dave Wolf
> > Internet Applications Division
> >
> > <=one way=> <oneway_111@yahoo.com> wrote in message
> > news:McVEpVwd$GA.149@forums.sybase.com...
> > > Isn't Sybase interested in fixing bugs? And if yes, why not fix issues
> > that
> > > were confirmed in a newsgroup as a bug?
> > >
> > > Dave Wolf [Sybase] <dwolf@sybase.com> wrote in message
> > > news:6YRHFKwd$GA.332@forums.sybase.com...
> > > > Peter,
> > > >
> > > > These newsgroups are not a replacement for technical support. There
> is
> > > > absolutely no guarantee that a bug reported on these newsgroups will
> be
> > > > fixed. As you've noted, they rarely are. If youhave a bug please
> open
> > a
> > > > technical support case so these things dont go unfixed for a year.
> > > >
> > > > Dave Wolf
> > > > Internet Applications Division
> > > >
> > > > Peter Reedijk <peter.reedijk@pica.nl> wrote in message
> > > > news:34brYGwd$GA.327@forums.sybase.com...
> > > > > The message below was posted more than half a year ago in this
> > > newsgroup.
> > > > > Several fixes later, I've tried to implement PrintOpen() etc. Still
> > > > returns -1,
> > > > > so bug doesn't look fixed yet. Can anyone confirm this?
> > > > >
> > > > > Furthermore, on Solaris datastore.Print() also doesn't work
> > > (returns -1).
> > > > Is
> > > > > that also a known bug?
> > > > >
> > > > > TIA
> > > > > Peter
> > > > >
> > > > >
> > > > > (quote)
> > > > > If you want to print a datawindow from PB/Jag component, currently
> you
> > > can
> > > > use
> > > > > <dw obj>.Print()
> > > > >
> > > > > We have noticed that in a PB/Jag component if you use PrintOpen()
> and
> > > then
> > > > > functions such as PrintDataWindow(), PrintText(), PrintLine() etc,
> > they
> > > > fail
> > > > > with -1 return code. A bug (cr 201828) has been opened against this
> > > > problem. Not
> > > > > ETA for fix....
> > > > >
> > > > > HTH
> > > > > (unquote)
> > > >
> > > >
> > >
> > >
> >
> >

--
===============================================================================
Lance J. Andersen Email: lancea@sybase.com
Sybase Product Support Engineering Phone:(781) 564-6336
77 South Bedford Street Fax: (781) 564-7001
Burlington, MA 01803

The Dark Knight Returns!!! Let's Go Penguins!!!
===============================================================================