joanneabator
Technical User
- Jul 9, 2003
- 7
So bizarre I'm not even sure how best to describe the problem!
We have a VB6 application which populates temporary Access tables ... in this instance a report of payments for a given payment date. The code consisently writes the correct data to the Access Tables. The report displays through CRViewer91 properly the first time. On subsequent displays, the report drops the number of units for the last payee, which impacts the running total of units. We look ... the data is in the table. We launch the Crystal Report directly, the data is there and displays properly.
BTW, we do execute
CRViewer91.Refresh
BEFORE
CRViewer91.ViewReport
Interestingly enough, this problem appears for only one of eight fields reported per records, and only on the final of 18 records.
Is anyone familiar with any bugs in the CRviewer91 that might account for this crazy result? Any and all insights would be greatly appreciated.
Thanks,
Joanne
We have a VB6 application which populates temporary Access tables ... in this instance a report of payments for a given payment date. The code consisently writes the correct data to the Access Tables. The report displays through CRViewer91 properly the first time. On subsequent displays, the report drops the number of units for the last payee, which impacts the running total of units. We look ... the data is in the table. We launch the Crystal Report directly, the data is there and displays properly.
BTW, we do execute
CRViewer91.Refresh
BEFORE
CRViewer91.ViewReport
Interestingly enough, this problem appears for only one of eight fields reported per records, and only on the final of 18 records.
Is anyone familiar with any bugs in the CRviewer91 that might account for this crazy result? Any and all insights would be greatly appreciated.
Thanks,
Joanne