page breaks in report view vs. print preview

[the_net_2.0]

all,

Can't figure this out either. I need to have a report open in report view because I have a button that closes it and returns to the form behind it.

However, my "force new page" property AND the page break CONTROL doesn't seem to work in report view. Neither of them work, that is. Anyone know a workaround for this?

I think I can somehow pull off a trick using the "sorting and grouping" interface funcationality for the reports, but there is no grouping needed for the dataset.

What I'm looking for is a scenario where I can have one record on each page of the report, but also having the ability to click the close button. You can't do that in print preview mode.

Anyone help with this please? Google doesn't seem to turn up anything about this scenario. thanks!

 

[vbaInet]

What I'm looking for is a scenario where I can have one record on each page of the report, but also having the ability to click the close button. You can't do that in print preview mode.

You can't get it both the_net_2.0

Report view shows a full page, no page breaks, no repeatable sections, no nothing

Just use print preview and get the users to click the X button to close the report.

Idea: Try using subforms. Subform 1 will display the first 10 records, subform 2 will show the next 10 ... etc.

 

[the_net_2.0]

Just use print preview and get the users to click the X button to close the report.

the problem I have found with this is that regardless of the border style you have on the report, you can double click on the border itself and minimize the thing. That messes everything up, because when that happens and even if the report is set to modal AND popup both, it loses those properties and can disappear behind other objects when it's minimized by the border double-click.

However, I've noticed that if I set the border to none, the only way to get out of the report if the 'X' is not there, is to press ALT+F4. Right now, that's what I've got. I am telling the users that they have to look at the report in preview mode, click from page to page with the arrows at the bottom and then close it by way of the keyboard.

It seems to still be available, even when you turn off the 'Use Special Keys' option.

 

[vbaInet]

the problem I have found with this is that regardless of the border style you have on the report, you can double click on the border itself and minimize the thing. That messes everything up, because when that happens and even if the report is set to modal AND popup both, it loses those properties and can disappear behind other objects when it's minimized by the border double-click.

I don't see how this is possible with a Dialog border style. Can you upload a mock up for me to see.

Explain what you would ideally like it to be as well once you've done that.

 

[the_net_2.0]

I don't see how this is possible with a Dialog border style. Can you upload a mock up for me to see.

Explain what you would ideally like it to be as well once you've done that.

I already offered the explanation, sir. It's a few posts ago. See previous for what I would like to see.

I attached a sample of the report being opened up with a dialog border. notice that when it opens, I maximize it with code. then on close, I minimize it.

could this one liner of code be the culprit of why the border can still be double clicked? that actually might be it. but again, what's the workaround?

open the only form in it and create a report. you'll see what I'm referring to. make sure to double click the rpt's border to minimize it.

 

[vbaInet]

Have a look at the attached. Use the form, frmOpenCOA to open the report.

 

[the_net_2.0]

Have a look at the attached. Use the form, frmOpenCOA to open the report.

so simply adding ''restore'' and the ''window height'' properties to what I already did gets me to where I want to be?

is that about it?

 

[vbaInet]

No, the timer is relevant too.

 

[the_net_2.0]

No, the timer is relevant too.

and why is that?

 

[vbaInet]

That little delay is needed or else the MoveSize command won't fire. Try it out. In the On Open or On Load event of the report:

DoCmd.Maximize
DoCmd.Restore
DoCmd.MoveSize 0,0,5000,5000

...and the Restore is need for MoveSize to work too.

 

[the_net_2.0]

OK I will try.

do you think it would be a wise idea to up the width and height args to something like 20,000 instead?

that doesn't make sense really, but the movesize args are twips:

1440 twips = 1 inch.

so if someone looks at the rpt on a 40 inch screen? Not likely, but aren't laptops 15" at the norm width?

 

[vbaInet]

The approach I used doesn't worry about the dimensions of the screen. It works like this:

1. Max the report
2. Get the window height and width and save into variables
3. Restore the report
4. Expand the report using the dimensions from step 2

So whether the screen is 15" or 40" the report will always fill up the screen when opened. There are APIs that you could use to get the screen's dimensions but I didn't bother looking for them.