 | | From: | John Fried | | Subject: | Plus 2.5 printing problem status?? | | Date: | Wed, 05 Jan 2005 16:59:16 -0500 |
|
|
 | How can I find out if the memory regression bug when printing on a Windows
98 box has been fixed in 2.5? Sorry, I don't have the QAID number and the
search by filter option doesn't work on the website any more. It was
reported about six months ago. There was no mention of this fix in the
release notes. I have several clients still using dB2K until this can be
fixed.
Also (yeah, I know, only one request per post) when can we expect a fix
to the reported print problems (chooseprinter and headerband)? I don't need
a specific date but are we talking weeks, months...? The chooseprinter bug
is another "show-stopper" item preventing me from updating my clients to
2.5 (and me from using it).
Thanks,
John
|
|
| | From: | Marty Kay | | Subject: | Re: Plus 2.5 printing problem status?? | | Date: | Wed, 5 Jan 2005 18:27:52 -0500 |
|
|
| Hi John,
> How can I find out if the memory regression bug when printing on a Windows
> 98 box has been fixed in 2.5? Sorry, I don't have the QAID number and the
> search by filter option doesn't work on the website any more. It was
> reported about six months ago. There was no mention of this fix in the
> release notes. I have several clients still using dB2K until this can be
> fixed.
I believe this was fixed in the 2.5 release via:
QAID: 4892 - Fixed GDI resource leak after editing a report in the report
designer
This description should have read:
GDI Resource leak after editing a report in the report designer OR
when running report.
> Also (yeah, I know, only one request per post) when can we expect a fix
> to the reported print problems (chooseprinter and headerband)? I don't
need
> a specific date but are we talking weeks, months...? The chooseprinter bug
> is another "show-stopper" item preventing me from updating my clients to
> 2.5 (and me from using it).
Fixes for chooseprinter() and headerband.height are in beta test now.
We are working on several more issues that we would like to include in the
2.51 release.
When they are done we will release it.
Thanks for checking,
- Marty Kay (dBI) -
|
|
| | From: | John Fried | | Subject: | Re: Plus 2.5 printing problem status?? | | Date: | Thu, 06 Jan 2005 09:53:13 -0500 |
|
|
| Hi Marty,
Thanks for the quick reply!
> I believe this was fixed in the 2.5 release via:
> QAID: 4892 - Fixed GDI resource leak after editing a report in the report
> designer
>
> This description should have read:
> GDI Resource leak after editing a report in the report designer OR
> when running report.
I read that in the release notes but thought it was for a different bug. I
tried to look up QAID 4892 but the dBASE Bug Reports website is still
broken.
As I recall, the QAID that reported the runtime leak was first reported by
someone from Italy(?) and I was a Me Too'er on it. Since I have two major
clients still running Windows 98 (who both reported the problem to me
within days of upgrading to 2.21), I really need to make sure it was fixed
before moving them back to 2.x from dB2K (I'm running Windows 2000 so I
can't test).
> Fixes for chooseprinter() and headerband.height are in beta test now.
>
> We are working on several more issues that we would like to include in the
> 2.51 release.
> When they are done we will release it.
I'll keep waiting (and using dB2K). FWIW, before 2.51 can be usable by my
clients, the 2.51 runtime installer must also be released. It does me no
good to write apps in 2.51 if my clients can't run it. But you knew that
already... ;-)
Thanks again,
John
|
|
| | From: | John Fried | | Subject: | Re: Plus 2.5 printing problem status?? | | Date: | Thu, 06 Jan 2005 11:24:17 -0500 |
|
|
| Marty,
I found the original dbase.bug-reports post from Vasile Buza on 5/18/04
with the Subject: "GDI resource leak with report class in dbasePlus v2.21
(b1755) & Win 9x".
I couldn't view the replies so I don't know the assigned QAID number.
Hope this helps track it down...
John
John Fried wrote:
>
> As I recall, the QAID that reported the runtime leak was first reported by
> someone from Italy(?) and I was a Me Too'er on it.
|
|
| | From: | Vasile Buza | | Subject: | Re: Plus 2.5 printing problem status?? | | Date: | Fri, 7 Jan 2005 07:04:02 +0200 |
|
|
|
"John Fried" wrote in message
news:41DD6631.6974A21B@dataknight.com...
> Marty,
>
> I found the original dbase.bug-reports post from Vasile Buza on 5/18/04
> with the Subject: "GDI resource leak with report class in dbasePlus v2.21
> (b1755) & Win 9x".
>
Hi John,
QAID: 4892 it was fixed in builds 1804 & 1807(runtime). No more problems in
Win 9x.
But you must pay attention to the height properties of all bands...
Vasile Buza
|
|
| | From: | John Fried | | Subject: | Re: Plus 2.5 printing problem status?? | | Date: | Fri, 07 Jan 2005 09:08:12 -0500 |
|
|
| Hi Vasile,
Thank you for confirming that this has been fixed. I can revise my reports
to fix the headerband problem but I still must wait for the ChoosePrinter
fix before I can use 2.5 for my clients. Fix one... break another...
;-)
Thanks again,
John
Vasile Buza wrote:
>
> QAID: 4892 it was fixed in builds 1804 & 1807(runtime). No more problems in
> Win 9x.
> But you must pay attention to the height properties of all bands...
|
|
