Inconsistent Report Preview Output Access 2003

Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data is
there sometimes not. Some records on the subreport are shown, some are not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I don't
get any error messages. Each individual subreport appears to work. Again, it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve

What query are you using to "feed" your reports? Your sub-reports?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve" wrote in message
...
Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data
is
there sometimes not. Some records on the subreport are shown, some are
not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I
don't
get any error messages. Each individual subreport appears to work. Again,
it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it
right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve

I have heard of this if you are using certain types of coding that aggregates
values or performs other tasks. This might also occur if your report or
record sources rely on values from forms that get closed too early.

--
Duane Hookom
Microsoft Access MVP


"Jeff Boyce" wrote:

What query are you using to "feed" your reports? Your sub-reports?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve" wrote in message
...
Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data
is
there sometimes not. Some records on the subreport are shown, some are
not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I
don't
get any error messages. Each individual subreport appears to work. Again,
it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it
right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve


.

This is the control source of one of the textboxes on one of the subreports
and is the most complicated. It appears that Access does not handle this
well. Will the performance be improved if I output the report to microsoft
word or is there another work around?

=Trim("Base Rhythm: " & [chrBaseRhythm] & ("; Rhythm Induced:
"+[chrObsIndRhythm]) & ("; Induction Method: "+[chrInductionMethod]) & (";
Sub-protocol: "+[chrSubProtocol]) & ("; Pacing Site "+[chrPacingSite]) & (";
S1:S1 "+Str([intS1S1])) & (" x "+Str([intDriveTrainL])+" beats") & (";
Starting c.l. "+Str([intStartCL])) & ("; Ending c.l. "+Str([intEndCL])) & (";
Drug Dose "+Str([intDrugDose])+" "+[chrDrugUnits]) & ("; S1:S2
"+Str([intS1S2])) & ("; S2:S3 "+Str([intS2S3])) & ("; S3:S4 "+Str([intS3S4]))
& ("; Ablation Target: "+[chrAblationTarget]) & ("; Ablation Attempt# :
"+Str([intAblAttemptNo])) & ("; Ablation Catheter: "+[chrAblCath]) & (";
Ablation Sheath: "+[chrAblSheath]) & ("; Approach: "+[chrAblApproach]) & (";
Catheter Position: "+[chrCatheterPosition]) & ("; Rhythm During Ablation:
"+[chrAblRhythm]) & ("; Ablation Control: "+[chrAblControl]) & (";
Consolidation Lesion: "+[chrConsolidation]))
--
Steve


"Duane Hookom" wrote:

I have heard of this if you are using certain types of coding that aggregates
values or performs other tasks. This might also occur if your report or
record sources rely on values from forms that get closed too early.

--
Duane Hookom
Microsoft Access MVP


"Jeff Boyce" wrote:

What query are you using to "feed" your reports? Your sub-reports?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve" wrote in message
...
Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data
is
there sometimes not. Some records on the subreport are shown, some are
not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I
don't
get any error messages. Each individual subreport appears to work. Again,
it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it
right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve


.

Are you mixing "+" and "&" intentionally in your expression?
Have you tried moving the expression to the query to see if that helps?
Have you tried different printers? How about the Microsoft Office Document
Image Writer?

--
Duane Hookom
Microsoft Access MVP


"Steve" wrote:

This is the control source of one of the textboxes on one of the subreports
and is the most complicated. It appears that Access does not handle this
well. Will the performance be improved if I output the report to microsoft
word or is there another work around?

=Trim("Base Rhythm: " & [chrBaseRhythm] & ("; Rhythm Induced:
"+[chrObsIndRhythm]) & ("; Induction Method: "+[chrInductionMethod]) & (";
Sub-protocol: "+[chrSubProtocol]) & ("; Pacing Site "+[chrPacingSite]) & (";
S1:S1 "+Str([intS1S1])) & (" x "+Str([intDriveTrainL])+" beats") & (";
Starting c.l. "+Str([intStartCL])) & ("; Ending c.l. "+Str([intEndCL])) & (";
Drug Dose "+Str([intDrugDose])+" "+[chrDrugUnits]) & ("; S1:S2
"+Str([intS1S2])) & ("; S2:S3 "+Str([intS2S3])) & ("; S3:S4 "+Str([intS3S4]))
& ("; Ablation Target: "+[chrAblationTarget]) & ("; Ablation Attempt# :
"+Str([intAblAttemptNo])) & ("; Ablation Catheter: "+[chrAblCath]) & (";
Ablation Sheath: "+[chrAblSheath]) & ("; Approach: "+[chrAblApproach]) & (";
Catheter Position: "+[chrCatheterPosition]) & ("; Rhythm During Ablation:
"+[chrAblRhythm]) & ("; Ablation Control: "+[chrAblControl]) & (";
Consolidation Lesion: "+[chrConsolidation]))
--
Steve


"Duane Hookom" wrote:

I have heard of this if you are using certain types of coding that aggregates
values or performs other tasks. This might also occur if your report or
record sources rely on values from forms that get closed too early.

--
Duane Hookom
Microsoft Access MVP


"Jeff Boyce" wrote:

What query are you using to "feed" your reports? Your sub-reports?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve" wrote in message
...
Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data
is
there sometimes not. Some records on the subreport are shown, some are
not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I
don't
get any error messages. Each individual subreport appears to work. Again,
it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it
right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve


.

Thanks for your thoughts Duane. I am going to try moving the expression into
a query and see if that helps.
--
Steve


"Duane Hookom" wrote:

Are you mixing "+" and "&" intentionally in your expression?
Have you tried moving the expression to the query to see if that helps?
Have you tried different printers? How about the Microsoft Office Document
Image Writer?

--
Duane Hookom
Microsoft Access MVP


"Steve" wrote:

This is the control source of one of the textboxes on one of the subreports
and is the most complicated. It appears that Access does not handle this
well. Will the performance be improved if I output the report to microsoft
word or is there another work around?

=Trim("Base Rhythm: " & [chrBaseRhythm] & ("; Rhythm Induced:
"+[chrObsIndRhythm]) & ("; Induction Method: "+[chrInductionMethod]) & (";
Sub-protocol: "+[chrSubProtocol]) & ("; Pacing Site "+[chrPacingSite]) & (";
S1:S1 "+Str([intS1S1])) & (" x "+Str([intDriveTrainL])+" beats") & (";
Starting c.l. "+Str([intStartCL])) & ("; Ending c.l. "+Str([intEndCL])) & (";
Drug Dose "+Str([intDrugDose])+" "+[chrDrugUnits]) & ("; S1:S2
"+Str([intS1S2])) & ("; S2:S3 "+Str([intS2S3])) & ("; S3:S4 "+Str([intS3S4]))
& ("; Ablation Target: "+[chrAblationTarget]) & ("; Ablation Attempt# :
"+Str([intAblAttemptNo])) & ("; Ablation Catheter: "+[chrAblCath]) & (";
Ablation Sheath: "+[chrAblSheath]) & ("; Approach: "+[chrAblApproach]) & (";
Catheter Position: "+[chrCatheterPosition]) & ("; Rhythm During Ablation:
"+[chrAblRhythm]) & ("; Ablation Control: "+[chrAblControl]) & (";
Consolidation Lesion: "+[chrConsolidation]))
--
Steve


"Duane Hookom" wrote:

I have heard of this if you are using certain types of coding that aggregates
values or performs other tasks. This might also occur if your report or
record sources rely on values from forms that get closed too early.

--
Duane Hookom
Microsoft Access MVP


"Jeff Boyce" wrote:

What query are you using to "feed" your reports? Your sub-reports?

--

Regards

Jeff Boyce
Microsoft Access MVP

Disclaimer: This author may have received products and services mentioned in
this post. Mention and/or description of a product or service herein does
not constitute endorsement thereof.

Any code or pseudocode included in this post is offered "as is", with no
guarantee as to suitability.

You can thank the FTC of the USA for making this disclaimer
possible/necessary.

"Steve" wrote in message
...
Hi,

I have a fairly complicated report in Access 2003 with sub-reports. When I
preview the report, I get inconsistent results. Sometimes sub-report data
is
there sometimes not. Some records on the subreport are shown, some are
not.
Some of the formating is shown correctly, sometimes not. Sometimes what is
displayed on the screen and what is printed are 2 different things. I
don't
get any error messages. Each individual subreport appears to work. Again,
it
is the inconsistentcies that seem odd. Itis like a very small artist is
making a thumbnail sketch of the report and sometime he or she gets it
right,
sometimes not. Is this a known flaw in Microsoft Access and is there a way
around this?
--
Steve


.