Print Report, disable restore button. Inconsistencies.

[mafhobb]

I have a database with several reports that get constantly printed, however I am having an issue with their display properties that sometimes cause errors.

I need the report to come up on top of everything, maximized and with the menu bar available to allow for it to be printed or close it. The report window cannot have "minimize" or "restore" available to make sure nobody access any form behind it.

To achieve this in a form I generally use the modal property, however if I do this in a report I cannot get to the menu bar to print or close the print preview.

Thinking that modal was out of the question, I went ahead and maximized the report on load and set its properties to the image attached. The db is then compiled (accde) and then distributed.

On my computer (it is being developed on my machine) the report loads fine (maximized) with no min, max or restore buttons and the print preview menu bar is shown with the print and close buttons available. See "My PC" image attached.

On any other computer, the report opens up maximized but the report's restore and close buttons are enabled, however the print and close buttons on the print preview menu bar are greyed out. See "Other PC" image attached.

Why the inconsistent behaviour when using the same front end?

What am I missing? :banghead::banghead::banghead:

mafhobb

 

[marlan]

Hi,
I think you now have no close button either.
Try changing the From's Control box property to 'Yes'

 

[mafhobb]

Hi Marlan,

My issue is that using the current setup, the report opens fine in my computer and I get the options I want (no min, restore or close on the report's window but print and close on the print preview menu) however this is not how the same front end works on another computer. Why?

sportjet

 

[JHB]

Only a thought, does the other computer have a printer connected?
I see there are 2 different versions - English/German.

 

[mafhobb]

Yes, both computers have several printers connected. The printers are not the same.

And yes, one computer is offsite (mine, in English) while the other is connected to a network in a German company. The access version is the same (2010) although one is in German and the other one in English. The front end is the same file.

I create the first accde on my computer and perform all tests and then I connect to a virtual desktop on the German company's network, upload the same uncompiled front end and create the second accde. Then I run the same tests.

I have done this five times these last two days to see if I was doing something different, but even when creating the two accde at the same time (with two monitors, one viewing the virtual desktop and the other one my own access copy) and going step by step on all options, the end result is different...but only on this report issue.

mafhobb

 

[mafhobb]

Well, after much work on this issue, I created a new db and imported all the forms, queries, tables, etc to it.

Without any changes, the new db is 7Mb as opposed to 15Mb for the original. The problems described in this thread have dissapeared.

Right now it seems like I had some corruption issues somewhere. We'll see what happens in a few days.

mafhobb