detailrecord is not printed, serious problem!
Hi,
RB5.5 performed well on my master-detail report, but RB6.03 does not. I
think I know why, but I can't do anything about it!!
My master-detail:
Level1-->Level2-->Level3-->Level4-->Level5
Level 3 is the problem. Sometimes the LAST detailrecord is NOT printed.
I managed to track down the problem to the report-grouping on record
ID-numbers. I sort my recordsets on "name" (non unique key) but I group on
the corresponding unique ID-number (dbpipeline.ID). So ID-numbers are not
sorted.
The next two examples DO work. The first one because of the accidental
ascending indexes, the second because there is one following level2-record:
-The last Level2-record
---Level3 ID = 2
---Level3 ID = 5
-Level2-record
---Level3 ID = 5
---Level3 ID = 2
-Another Level2-record
The following example DOES NOT work because of the second L3-record having a
LOWER ID than the first L3-record !!!!!:
-The last Level2-record
---Level3 ID = 5
---Level3 ID = 2
So, now I have a serious-problem, because 60 customers can't print their
reports anymore.
Leon
RB5.5 performed well on my master-detail report, but RB6.03 does not. I
think I know why, but I can't do anything about it!!
My master-detail:
Level1-->Level2-->Level3-->Level4-->Level5
Level 3 is the problem. Sometimes the LAST detailrecord is NOT printed.
I managed to track down the problem to the report-grouping on record
ID-numbers. I sort my recordsets on "name" (non unique key) but I group on
the corresponding unique ID-number (dbpipeline.ID). So ID-numbers are not
sorted.
The next two examples DO work. The first one because of the accidental
ascending indexes, the second because there is one following level2-record:
-The last Level2-record
---Level3 ID = 2
---Level3 ID = 5
-Level2-record
---Level3 ID = 5
---Level3 ID = 2
-Another Level2-record
The following example DOES NOT work because of the second L3-record having a
LOWER ID than the first L3-record !!!!!:
-The last Level2-record
---Level3 ID = 5
---Level3 ID = 2
So, now I have a serious-problem, because 60 customers can't print their
reports anymore.
Leon
This discussion has been closed.
Comments
a group, because the group break is determined by a change in the group
break value. Can you send a working example to
support@digital-metaphors.com and we'll research this.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com
Sent you an example around 3-2-2002. I did'nt receive a reply from you so Im
not sure received it correctly ?
Leon
see the data records as they are ordered by your query.
Cheers,
Jim Bennett
Digital Metaphors Corp
http://www.digital-metaphors.com
info@digital-metaphors.com
in the report?
Cheers,
Jim Bennett
Digital Metaphors Corp
http://www.digital-metaphors.com
info@digital-metaphors.com
Now you received an example program including databasefile and
databasedrivers.
The only thing you need is DAO-drivers (office95 or office97).
I tried to emulate the problem using a paradox database but it seems it's
more database dependend than I thought.
Good luck,
Leon
Kevin suggested the problem is within OPUS and not RB603.
I would like to ask you again to look into the example and see that it's not
running ok, because all prevous versions of RB from version 4 worked
allright together with exactly the same OPUS version and the same report.
And I really like RB alot, but in order to run it, it must be able to handle
these master-detail reports.
Thanks,
Leon
done with a new bookmarking scheme. OPUS isn't able to handle bookmarks
correctly. We can't revert to the old way of traversing the dataset,
because many customers would be unhappy when their reports began running
incorrectly. OPUS needs to be fixed in order to support simple bookmarking
on the dataset. You may want to look into a different Database vendor.
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com