I have the pleasure of following another developer who cannot be contacted and who left no documentation. Access 2003, fairly simple tables layout. He consistenly has managed to place a "report within a report" in numerous reports. The application is invoicing; the "imbedded" report shows in design view as a one line scroll bar, left to right. When properties are turned on and I click on the scroll bar, the properties window just says "Report". The data source property is a table. The properties just do not seem to give me any information to solve the mystery of how it hangs together. Logic says the designer should have used a subreport, it's a natural to do so; the data are individual transactions associated with the invoice (special charges etc., there may be multiple lines, and it somehow works fine.) But it's definitely not a subreport.
But... I need to know how he did this. I am making enhancements and changes to this system. Can one "drag" an exisitng report into a new report under design? I don't see how this report works, or how he got this mystery report into the main report. There is no linkage (that I can find) between the table in the imbedded report and the primary table that drives the main report. There is little VBA behind the reports and what there is is pretty straightforward. The guy clearly did not understand database and table concepts and has written tons of near-duplicate reports just to deal with variations in conditions. I know this is not a brilliant explanation of the problem but I am realy baffled as to what I'm dealing with. Thanks in advance for your thoughts.
Regards,
Harry(xbigblue)
But... I need to know how he did this. I am making enhancements and changes to this system. Can one "drag" an exisitng report into a new report under design? I don't see how this report works, or how he got this mystery report into the main report. There is no linkage (that I can find) between the table in the imbedded report and the primary table that drives the main report. There is little VBA behind the reports and what there is is pretty straightforward. The guy clearly did not understand database and table concepts and has written tons of near-duplicate reports just to deal with variations in conditions. I know this is not a brilliant explanation of the problem but I am realy baffled as to what I'm dealing with. Thanks in advance for your thoughts.
Regards,
Harry(xbigblue)