We have a user who is experiencing this problem when attempting to open a report. Is the problem the rtm file corrupt? We are using RBP 5.0. The reports were built in RBP 5.0 and being opened in RBP 5.0.
(please change your news name, "Delphi User" isn't what we are expecting here, thanks)
Did you check the GlobalOnCreate event, does it compile without errors?
(BTW, you aren't using an actual ReportBuilder version, current version is 6.03, the update is for free, if you didn't got any mail with update informations, contact sales@digital-metaphors.com).
I don't want to upgrade to 6.03 right now because it would cause major issues. We have many, many customers using our product (maybe 10,000 users). Some users are remote and some are not. We have two separate applications that use RBP. If we upgrade to 6.03, it would cause ALL customers to UPGRADE ALL USERS. If a non-remote users upgrades to 6.03 and creates a report and sends that report to a remote user who hasn't upgraded, the report will not run and this will cause major issues. We have notified our customers that on 1/1/2002, all of our versions will include the latest version (6.03). We gave the customers 6 months notice.
Anyway, I believe I know what the issue is. Our consultant was doing logic on values that he assumed would not be blank but they really are. Therefore the code blows up.
Comments
(please change your news name, "Delphi User" isn't what we are expecting
here, thanks)
Did you check the GlobalOnCreate event, does it compile without errors?
(BTW, you aren't using an actual ReportBuilder version, current version is
6.03, the update is for free, if you didn't got any mail with update
informations, contact sales@digital-metaphors.com).
regards,
Chris Ueberall;
I don't want to upgrade to 6.03 right now because it would cause major
issues. We have many, many customers using our product (maybe 10,000 users).
Some users are remote and some are not. We have two separate applications
that use RBP. If we upgrade to 6.03, it would cause ALL customers to UPGRADE
ALL USERS. If a non-remote users upgrades to 6.03 and creates a report and
sends that report to a remote user who hasn't upgraded, the report will not
run and this will cause major issues. We have notified our customers that on
1/1/2002, all of our versions will include the latest version (6.03). We
gave the customers 6 months notice.
Anyway, I believe I know what the issue is. Our consultant was doing logic
on values that he assumed would not be blank but they really are. Therefore
the code blows up.