Pop Up Forms

[friedboudinball]

I have a form that i want to "pop up" because it focuses the emphasis, among other things. So, i selected the "pop up" property and it works great.

however, when you click on a button on the form (to open a new report, for example) the form stays "in front," as expected.

Is there a way around this, either progamatically, or some other way?

 

[Mr. B]

If you know that the popup form will not be needed again by the user, you can simple close that form during the same code that is opening the report.

If you want the popup form to still be available to the user then you can set the visibility of the form to false in the code that is opening the report. Then in the On Close event of the report you can check to see if the form is loaded and if so set the visibility of the form to true.

 

[missinglinq]

Or, you could simply set the Report's Popup Property to Yes, just like the Form's!

Linq ;0)>

 

[friedboudinball]

Or, you could simply set the Report's Popup Property to Yes, just like the Form's!

Linq ;0)>

Simple solution ... though you do have to make it Modal for it to pop in front. Kudos to Bob Larson for posting that elsewhere and me for noticing it!

Thanks again.

 

[missinglinq]

... though you do have to make it Modal for it to pop in front...

Not in Access 2003! Tested with both Form and Report set to

Popup = Yes

Modal = No

Linq ;0)>

 

[Mr. B]

I have tested using Access 2010 with form and report set to Popup and the report is presented in front of the form.

 

[friedboudinball]

Access 2007 doesn't work for some reason. however, i fixed by making it modal and maximizing. that forces user to address the report/form, etc.

thank you for your help.

 

[vbaInet]

Can you upload a stripped down version of your db and just tell us how to reproduce the problem.

 

[missinglinq]

Probably another bug in 2007, which was buggier than the Great Dismal Swamp! Bob was probably referring to 2007, as well.

Linq ;0)>

 

[vbaInet]

I've not had this problem. I mainly use 2007.

 

[missinglinq]

Maybe fixed with a service pack? Allen Browne doesn't list it as a known bug in 2007, but I suppose it could be.

Linq ;0)>

 

[vbaInet]

Hmmm... maybe missingling. I would have to see the db to verify this.

 

[missinglinq]

Hmmm... maybe missingling. I would have to see the db to verify this.

If the problem isn't present with the service pack you're running, how would that help? The question would be what service pack(s)/hotfixes you have installed versus what service pack(s)/hotfixes the OP has installed, wouldn't it? You can't look at his file and tell what he has installed, can you?

Linq ;0)>

 

[vbaInet]

It's still worth testing it with whatever service packs I have installed. No one has tested it in 2007 yet. You tested it in 2003, Mr. B in 2010. If it works on mine then we can infer that it's the service pack.