views:

388

answers:

1

ActiveReports seems like a powerful flexible tool, but if you make a mistake anywhere, you get an exception "data member not found. please check your datasource and datamember properties".

There is no indication as to which datasource/datamember is at fault or what subreport the problem lies in, but Active Reports must know this!

The stack trace is no use, as the error is thrown after the report.run() method is invoked from deep within code generated by Active Reports itself.

Does anybody have a solution other than commenting out one subreport after another and checking all fields in turn?

+1  A: 

Unfortunately I don't know a way to immediately tell which subreport that error is coming from. Indeed, that error message should be improved when you're using subreports. I will report it to the ActiveReports development team.

scott
ActiveReports team gave me case number 124157 to track the suggestiong of improving this error message in the future.
scott