469,160 Members | 2,083 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,160 developers. It's quick & easy.

Subreport not showing - but my frustration is

Damn this is frustrating. I have used subreports for years and never had
this problem. I have used these things more times than I can remember. Never
have I had this problem. Arrrgggghhhhhhhhhhhhhhhhhhhhhh.....etc and ahhh

This should be simple, but... This is a report for a sales order. Parent
report actually shows the header and detail, detail is not in the subreport.
In the subreport is a breakup of committed product by UseBy date.

Master and Child link fields are both 'OrderInvoiceNo;LineNo'. There are
records to show for the order the report is generated on.

The fields do exist in both the parent and sub reports.

If I remove the link fields the report shows heaps of records, as expected,
including the ones that should show for each detail. Add just the
OrderInvoiceNo and nothing shows. Add anything in the link fields and
nothing shows.

Why? Is it because it is Monday? Or maybe because I was having a good day?
Or am I just missing something so obvious here that it isn't?

And yes, I have restarted Access, which usually fixes illogical problems.
And gone and had some comfort food - snakes. Haven't got to the chocolate
yet. Cholesterol is too high for pizza. Chocolate doesn't count.

Jeff Pritchard
________________
Asken Research Pty. Ltd.
Access Database Developers (still)
www.asken.com.au

Feb 20 '06 #1
2 2986
Hi Jeff

No doubt there will be an obvious reason once the dust settles. :-)

In the mean time, is there any chance Access could misunderstand the data
type of any of these fields? Particularly:
- calculated fields may need to be typecast;
- query parameters may need to be declared (esp if applied to calculated
fields, or if reading a value from a control on a form);
- text boxes may need their Format property set if unbound, bound to an
expression, assigned programmatically, or bound to a calculated field.

Do the *controls* have the same name as the fields? If not, are you using
the control names in LinkMasterFields/LinkChildFields?

How are you limiting the date range for the subreport?

The subreport CanGrow?

You've probably tried a compact'n'repair (just in case there's a bad index.)

No doubt you already have the Name AutoCorrupt boxes unchecked (Tools |
Options | General.)

If none of that goes anywhere, what happens if you create a query based on
the main report's query joined to the subreport's query on OrderInvoiceNo
and LineNo?

BTW, there's a rumour that dark chocolate is supposed to be good for us?
:-)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <je************@asken.com.au> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...
Damn this is frustrating. I have used subreports for years and never had
this problem. I have used these things more times than I can remember.
Never have I had this problem. Arrrgggghhhhhhhhhhhhhhhhhhhhhh.....etc and
ahhh

This should be simple, but... This is a report for a sales order. Parent
report actually shows the header and detail, detail is not in the
subreport. In the subreport is a breakup of committed product by UseBy
date.

Master and Child link fields are both 'OrderInvoiceNo;LineNo'. There are
records to show for the order the report is generated on.

The fields do exist in both the parent and sub reports.

If I remove the link fields the report shows heaps of records, as
expected, including the ones that should show for each detail. Add just
the OrderInvoiceNo and nothing shows. Add anything in the link fields and
nothing shows.

Why? Is it because it is Monday? Or maybe because I was having a good day?
Or am I just missing something so obvious here that it isn't?

And yes, I have restarted Access, which usually fixes illogical problems.
And gone and had some comfort food - snakes. Haven't got to the chocolate
yet. Cholesterol is too high for pizza. Chocolate doesn't count.

Jeff Pritchard
________________
Asken Research Pty. Ltd.
Access Database Developers (still)
www.asken.com.au

Feb 20 '06 #2
Hi Allen

Oh what a difference a day makes.

I thought I had done all of those yesterday, but guess what - there was a
control named OrderInvoiceNo and that was the problem. Now I am sure I
checked that all controls had a prefix, 'txt' in this case. I think someone
is playing games with me. I'm not paranoid, really I'm not.

Time for some chocolate. We have to celebrate these little successes - don't
we.

Jeff Pritchard
________________
Asken Research Pty. Ltd.
Access Database Developers
http://www.asken.com.au

"Allen Browne" <Al*********@SeeSig.Invalid> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...
Hi Jeff

No doubt there will be an obvious reason once the dust settles. :-)

In the mean time, is there any chance Access could misunderstand the data
type of any of these fields? Particularly:
- calculated fields may need to be typecast;
- query parameters may need to be declared (esp if applied to calculated
fields, or if reading a value from a control on a form);
- text boxes may need their Format property set if unbound, bound to an
expression, assigned programmatically, or bound to a calculated field.

Do the *controls* have the same name as the fields? If not, are you using
the control names in LinkMasterFields/LinkChildFields?

How are you limiting the date range for the subreport?

The subreport CanGrow?

You've probably tried a compact'n'repair (just in case there's a bad
index.)

No doubt you already have the Name AutoCorrupt boxes unchecked (Tools |
Options | General.)

If none of that goes anywhere, what happens if you create a query based on
the main report's query joined to the subreport's query on OrderInvoiceNo
and LineNo?

BTW, there's a rumour that dark chocolate is supposed to be good for us?
:-)

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jeff" <je************@asken.com.au> wrote in message
news:43***********************@per-qv1-newsreader-01.iinet.net.au...
Damn this is frustrating. I have used subreports for years and never had
this problem. I have used these things more times than I can remember.
Never have I had this problem. Arrrgggghhhhhhhhhhhhhhhhhhhhhh.....etc and
ahhh

This should be simple, but... This is a report for a sales order. Parent
report actually shows the header and detail, detail is not in the
subreport. In the subreport is a breakup of committed product by UseBy
date.

Master and Child link fields are both 'OrderInvoiceNo;LineNo'. There are
records to show for the order the report is generated on.

The fields do exist in both the parent and sub reports.

If I remove the link fields the report shows heaps of records, as
expected, including the ones that should show for each detail. Add just
the OrderInvoiceNo and nothing shows. Add anything in the link fields and
nothing shows.

Why? Is it because it is Monday? Or maybe because I was having a good
day? Or am I just missing something so obvious here that it isn't?

And yes, I have restarted Access, which usually fixes illogical problems.
And gone and had some comfort food - snakes. Haven't got to the chocolate
yet. Cholesterol is too high for pizza. Chocolate doesn't count.

Jeff Pritchard
________________
Asken Research Pty. Ltd.
Access Database Developers (still)
www.asken.com.au


Feb 20 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Ellen Manning | last post: by
2 posts views Thread by GB | last post: by
3 posts views Thread by Matt | last post: by
2 posts views Thread by Ron | last post: by
reply views Thread by zhoujie | last post: by
1 post views Thread by Mortomer39 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.