Major Bug using MEMO fields in Reports

Major Bug using MEMO fields in Reports

Post by Don Mayle » Mon, 17 Aug 1998 04:00:00



I have encountered a "Major Bug" in Foxpro 2.6 for Windows.

When using MEMO fields that a larger than one page in a GROUP band,
Foxpro WILL NOT start the data on the first page if the data should
require a second page.  It should fill up the first page with the MEMO
data, then continue to the second page?

To reproduce this behavior

Use a single table with 2 fields
    ACCT_NO        character 8
    ACCT_NOTES  memo

Put the ACCT_NO in the detail band.
Create a group band by ACCT_NO and put the ACCT_NOTES field their.
Click the property "Field can stretch".

Insert enough text in the MEMO field (ACCT_NOTES) to require a second
page.
Preview the report

This Bug/Problem is really kicking my ass!
Any Ideas will be greatly appreciated!

Thanks in Advance!
Don

 
 
 

Major Bug using MEMO fields in Reports

Post by Hyperion Syste » Tue, 18 Aug 1998 04:00:00


Fox 2.6 has serious problems with memos in reports, as you have found.
There are only workarounds, but no solutions.  You can get 3rd party
report writers, which work well, but take some time to get used to.

One summer I did work for the government on a personnel system in 2.6.
One of the programmers was saddled with the daunting task of not only
getting the famed "Page X of Y" label working on a report, he also ran
into the problem you have encountered when memos run across pages and/or
groupings.  

Good thing the project was shelved after a few years and several million
of our tax dollars.

- John



Quote:>I have encountered a "Major Bug" in Foxpro 2.6 for Windows.

>When using MEMO fields that a larger than one page in a GROUP band,
>Foxpro WILL NOT start the data on the first page if the data should
>require a second page.  It should fill up the first page with the MEMO
>data, then continue to the second page?

>To reproduce this behavior

>Use a single table with 2 fields
>    ACCT_NO        character 8
>    ACCT_NOTES  memo

>Put the ACCT_NO in the detail band.
>Create a group band by ACCT_NO and put the ACCT_NOTES field their.
>Click the property "Field can stretch".

>Insert enough text in the MEMO field (ACCT_NOTES) to require a second
>page.
>Preview the report

>This Bug/Problem is really kicking my ass!
>Any Ideas will be greatly appreciated!

>Thanks in Advance!
>Don


 
 
 

Major Bug using MEMO fields in Reports

Post by Paul Duva » Wed, 19 Aug 1998 04:00:00


Hi Don

You're right, there's a problem with Memo fields in the group band.
But can you try this ?
In the group band, call a function instead of having your memo field there
Create a character field in the group band, and put in it MEMOHERE()
And in the main program, you should have :

FUNCTION MEMOHERE
?? ACCT_NOTES
RETURN ""

In Foxpro 2.5b for Dos, all the Memo field (75 lines) appears then correctly
in the Print Preview window

You'll probably have to change the value of Set Memowidth To

Maybe this idea can help you ?

Paul Duvall


>I have encountered a "Major Bug" in Foxpro 2.6 for Windows.

>When using MEMO fields that a larger than one page in a GROUP band,
>Foxpro WILL NOT start the data on the first page if the data should
>require a second page.  It should fill up the first page with the MEMO
>data, then continue to the second page?

>To reproduce this behavior

>Use a single table with 2 fields
>    ACCT_NO        character 8
>    ACCT_NOTES  memo

>Put the ACCT_NO in the detail band.
>Create a group band by ACCT_NO and put the ACCT_NOTES field their.
>Click the property "Field can stretch".

>Insert enough text in the MEMO field (ACCT_NOTES) to require a second
>page.
>Preview the report

>This Bug/Problem is really kicking my ass!
>Any Ideas will be greatly appreciated!

>Thanks in Advance!
>Don

   -**** Posted from Supernews, Discussions Start Here(tm) ****-
http://www.supernews.com/ - Host to the World's Discussions & Usenet
 
 
 

Major Bug using MEMO fields in Reports

Post by Don Mayle » Fri, 21 Aug 1998 04:00:00


Paul,

I tried what you recommended below in FPW 2.6.  Unfortunately it did not work :(

Have you been able to get this to work in the Windows version for Foxpro?


> Hi Don

> You're right, there's a problem with Memo fields in the group band.

> But can you try this ?

> In the group band, call a function instead of having your memo field there

> Create a character field in the group band, and put in it MEMOHERE()

> And in the main program, you should have :

> FUNCTION MEMOHERE

> ?? ACCT_NOTES

> RETURN ""

> In Foxpro 2.5b for Dos, all the Memo field (75 lines) appears then correctly

> in the Print Preview window

> You'll probably have to change the value of Set Memowidth To

> Maybe this idea can help you ?

> Paul Duvall


> >I have encountered a "Major Bug" in Foxpro 2.6 for Windows.

> >When using MEMO fields that a larger than one page in a GROUP band,

> >Foxpro WILL NOT start the data on the first page if the data should

> >require a second page.  It should fill up the first page with the MEMO

> >data, then continue to the second page?

> >To reproduce this behavior

> >Use a single table with 2 fields

> >    ACCT_NO        character 8

> >    ACCT_NOTES  memo

> >Put the ACCT_NO in the detail band.

> >Create a group band by ACCT_NO and put the ACCT_NOTES field their.

> >Click the property "Field can stretch".

> >Insert enough text in the MEMO field (ACCT_NOTES) to require a second

> >page.

> >Preview the report

> >This Bug/Problem is really kicking my ass!

> >Any Ideas will be greatly appreciated!

> >Thanks in Advance!

> >Don

>    -**** Posted from Supernews, Discussions Start Here(tm) ****-
> http://www.supernews.com/ - Host to the World's Discussions & Usenet

 
 
 

1. Major major MAJOR bug in BDE

I have (unfortunately) discovered a rather severe bug in the Borland Database
Engine.  To be brief: passthrough (RequestLive = TRUE) SQL queries cause a memory
leak in IDQRY01.DLL.

It may be specific to my SQL-LINK (ORACLE) but every TQuery.Open and every Master
Query DataChange in a Master-Detail Query causes a leak of about 5k from the
IDQRY01.DLL memory allocation (for EVERY TQUERY).  After 1700 of these leaks,
IDQRY01.DLL reports an EOutOfMemory exception, and must be unloaded and reloaded
to continue.

1700 sound like a lot?  Not if you have 10 detail queries, like I do.  That's
right kiddies, hit the (Master query TDBNavigator) Prior or Next buttons 170 times
and your program will crash.  And so will Paradox and every other BDE program you
have running.

What did Borland say when I reported it?  "Call our 1-900 line for help."  I am
going to pay Borland to let me help them debug a program I just got done paying
them $1700 for?  How nice of me!

I have been able to reproduce it on every machine I have tried (rather, I haven't
been able to not produce it, which really was the effect I was after.)  You can
watch it too: grab HeapWalker or whatever memory leak debugger you like to use and
watch IDQRY01.DLL's private allocations: when they reach 8.5 megs watch what
happens.  Neeto!  This is an especially nifty side effect when your project is
due, and Borland won't return your calls.

This can be demonstrated without a single line of code, just slap down two
TQuery's in a Master-Detail relationship, hook a TDBNavigator up to the master
DataSource, make sure the Detail TQuery is set up with RequestLive = TRUE.  Run.  
Hit the Navigator buttons about 1700 times.  (The preferred demo uses a TTimer to
automate the process, but that would require a single line of code ;-)

It does not happen with TTables or Local-SQL TQuerys.  (But I NEED to use
passthrough TQuerys!)

Disgruntled,

        Brian Badger
        MCI Telecommunications

--
Brian Badger, Registered Telepath; P -3 (I can't even read my own thoughts...)
My opinions are my own, and do not reflect the views of the Psi Cop who
implanted my personality.

2. Need Help with Master/Detail Table

3. GPF using memo fields i Crystal Reports...

4. Disappearing data!!!

5. Report Designing [Using Memo Field]

6. Heterogeneous Data Updates

7. Indent in memo-field, used in REPORT

8. Exporting database via .sql

9. Using memo fields in FOXPRO2 reports

10. Indentation of memo fields - reports vs. modify memo

11. Crystal Reports Professional 7- Memo fields will not appear on report

12. Making Crystal Reports display memo fields without messing up other parts of the report

13. Major bug using Access database in Delphi 3