This action can't be carried out while processing a form or report event

[data808]

Nope. Manually opening the report or opening it from a form does not make a difference. Mysteries...

[June7]

You do know what's next if you want more help? Only thing left is to provide the db for analysis.

[data808]

TESTPrintSetupButton.accdb

Hope this works!

[data808]

Ok I attached the file. I created a brand new db and its doing it for both print buttons. After you click the print buttons and the print window opens up, click on setup and let me know what happens. Like I mentioned before, I don't think I EVER got this setup button to work. I used to just ignore it and think nothing of it but now I would like to see what is causing this problem.

[trevor40]

Refer to my latest post. I replicated this on a brand new blank form. Nothing was changed. I went straight ahead and made the print buttons. Did not touch any other properties.

If you did the same thing don't you also expect the same result!!!!!!!!!!!

Did you try your report as an AcNormal in stead of AcDialog ?????????

Refer to my post # 9 IS THE FORM SET TO MODAL?
Without testing this I won't be offering any more help for you.

[data808]

Nothing was changed meaning I left the properties to default. Access defaults Pop Up to NO and Modal to NO. The original report came from a pop up and modal environment. The blank was not pop up and modal so I have tried both if thats what you meant?

The report is sizable, not dialog. Is that the same thing you're talking about?

To answer your question about the modal AGAIN, just for you, I tested it with Modal set to yes and modal set to no. There was no difference. I am beginning to think that something is wrong with my copy of Office 2007. In Post #18 I attached a sample database that also gives me the same error with the print setup button. Please try it out for me and if you are able to get access to the setup options, then this is just completely beyond me because it DOES NOT WORK FOR ME AND IF IT WORKS FOR YOU THEN I DO NOT KNOW WHAT IS GOING ON ANYMORE BECAUSE NO ONE, AND I MEAN NO ONE SEEMS TO HAVE THIS PROBLEM EXCEPT FOR ME AND THAT IS ONE BIG MYSTERY.

[trevor40]

O well, the only thing left is to post a copy in mdb format.

[data808]

Did the accdb that I attached work for you on print setup?

[June7]

I have your db. I click the buttons and the Print dialog opens. The ribbon is not even available at this point. The code works. Ah Ha. It is the Setup button on the Print dialog that triggers this error. Got it!

However, File > Print > Print does allow the Setup button to work. So now we have an answer. Initiating the Print dialog with code won't allow PageSetup from the Print dialog.

[data808]

So what is the fix? Is it impossible to be able to use the print setup from dialogue window?

[trevor40]

I think from a previous post you are trying to disable user access to various parts of your system, this could interfear with your problem.

create a blank db, import all objects, remove all vba code, inc report button code.

can you get to print options by clicking on the menu and selecting page setup from there?

if so, now add your button on the form to do this with vba.

If you can stiil get to the options, start adding one by one the lines of code that you use to limit user access to the system and menu

if you can find what is causing the problem post back the result, if not post your db in mdb format.

[June7]

Can't use PageSetup if Print dialog is triggered by code.

I tested

DoCmd.RunCommand acCmdPageSetup

That triggers the same error message.

[trevor40]

You could investigate...

DoCmd.DoMenuItem

[trevor40]

If all else fails perhaps you could use vba to make your own print setup dialog form and use that? No idea if it would work.

[data808]

I just did make a blank db and didn't do ANYTHING except make two buttons. One button made with with the control wizard to print. The other made with VBA. I used this command:

DoCmd.RunCommand acCmdPrint

For both of these buttons, I click it, then the print dialogue comes up. I click the setup button and then the error comes up. So I'm basically saying that it does not work in my current database with all the vba and macros going on AND it does not work when I start a freshly new database with the bare minimum of having just those print buttons. I swear, I am 99% sure that I have NEVER gotten this print setup to work in any of my databases. Like I mentioned before, I remember getting this problem a long time ago but never paid much attention to it till recently because I wanted to actually use it this time but by the looks of it, I guess its a glitch in Access that is not fixable. Either that or my copy of Access is defective. One or the other.