Data not appearing
What possible reasons are there that data that appears in the DADE display
should not cause a sub-report to show up? That is, it appears that at run
-time there is no data to report.
I have a query that if I preview will show the right information. If I
copy the magic SQL to SQL Server Query Analyzer and running it there gives
the same results. But the report that depends on it doesn't show.
The sub-report is a sub-report, and the query is a query that is linked to
query for the parent report. This works for other things, but seems to
stop at the third level. To be clear, my structure is:
MAIN REPORT
+--- Hierarchy parent
+--- Hierarchy child
+--- Detail output child
+--- Detail output parent
The query is:
Hierarchy Parent
<--- Hierarchy Child
<--- Detail data (filtered on main value)
The detail data for the hierarchy parent doesn't have the hierarchy child
in the way, and it works.
I'd much appreciate clues as to how to get around this!
/Matthew Jones/
should not cause a sub-report to show up? That is, it appears that at run
-time there is no data to report.
I have a query that if I preview will show the right information. If I
copy the magic SQL to SQL Server Query Analyzer and running it there gives
the same results. But the report that depends on it doesn't show.
The sub-report is a sub-report, and the query is a query that is linked to
query for the parent report. This works for other things, but seems to
stop at the third level. To be clear, my structure is:
MAIN REPORT
+--- Hierarchy parent
+--- Hierarchy child
+--- Detail output child
+--- Detail output parent
The query is:
Hierarchy Parent
<--- Hierarchy Child
<--- Detail data (filtered on main value)
The detail data for the hierarchy parent doesn't have the hierarchy child
in the way, and it works.
I'd much appreciate clues as to how to get around this!
/Matthew Jones/
This discussion has been closed.
Comments
If you have your data displaying correctly in DADE and the Magic SQL works
correctly in SQL Server, there are no known reasons why it would not be
showing up in your report. Are you able to recreate this behavior using one
of our provided demo applications? Are you in any place trying to alter the
data or report objects in some event code? If possible please send a small
simple example, using the DBDEMOS database that demonstrates this issue and
I will take a look at it for you. Please send the example in .zip format to
support@digital-metaphors.com.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
real data is cyclical), but could you tell me which type of database and
sqlType to use? I'm using ADO, and can connect to the DBDEMO data, but it
is creating SQL with "cust.orderno orderno_2," in which is being rejected.
I've tried Paradox, Access, and LocalSQL, but cannot get it to accept it.
/Matthew Jones/
I'm unclear about the issue now. Are you able to run our demo applications
that connect to the DBDEMOS database using paradox? If so, use this as a
reference to creating your own example app that demonstrates the original
problem and I will take a look at it for you.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
connect. I didn't want to go trawl all the demos to find out which one
might match my requirements. After all, the ADOConnection is probably a
key part of the problem - all the data is coming from that one connection.
But I can't get it to read the DBDEMO data properly without errors in the
SQL because, I think, I don't have the right data source type set.
/Matthew Jones/
Are you connecting to the DBDEMOS Access database? If so, are you able to
connect successfully using the TADOConnection (i.e. when you press "Test
Connection")? For an example of connecting to an Access database usind ADO,
see the example in the \RBuilder\Demos\4. EndUser Databases\Access 97\2.
ADO\... directory.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
seem able to cope. I couldn't get the demo database to work at all
sensibly given it doesn't have the same sort of data, and I was just
wasting time trying to replicate it. I can only conclude that
ReportBuilder is not able to cope with the complex data hierarchy in the
same table. The situation is a sub-report in a sub-report both looping on
data from the same table, determined by a hierarchy stored in another
table. RB probably could do it, but after days of experimentation I can't
afford more time to learn the underlying system to work out how it can be
cajoled into doing it.
I'll use it for other projects still though, so I'll be back!
/Matthew Jones/