Report Opening

[Beany]

hi,

i have a form that has two buttons......................

one button opens a form with a combobox.............. this combobox has a list of usernames(from the table)........ When selecting a username, it brings up a report with the users details.

the other button opens a report of all users...........

THE PROBLEM that i have is... when it opens the report whether from the combobox or directly from a button..... the report is displayed behind the all the forms.. i have to close down the forms to view the report...........y is that?

and also if i select from the combobox, i must close down the combobox screen to actually view or access the report????:(

[NeoPa]

Try adding this line of code to your report's OnOpen event procedure :

Call DoCmd.SelectObject(ObjectType:=acReport, ObjectName:=Me.Name)

[NeoPa]

If that doesn't help you must have some code in your project (running after the report is displayed) that selects the form again and brings it to the front.

[Beany]

can you explain that code to me?

im using the following code for my combobox:

DoCmd.OpenReport "Report2", acPreview, "", "[userID]=[Forms]![comboreport]![Combo0]"

[NeoPa]

Not much to explain really.
It selects the report object and brings it to the front of the window.

[MMcCarthy]

At a guess I would say you have the Modal property on your forms set to yes.

Mary

[Beany]

my pop up and modal are all set to NO....

Call DoCmd.SelectObject(ObjectType:=acReport, ObjectName:=Me.Name) 

In ObjectName:=Me.Name, do i change Me.Name to my report name?

my report is called Report2

[NeoPa]

my pop up and modal are all set to NO....

Call DoCmd.SelectObject(ObjectType:=acReport, ObjectName:=Me.Name) 

In ObjectName:=Me.Name, do i change Me.Name to my report name?

my report is called Report2

No, that's exactly as it needs to be.
I'm not hopeful it will work, but it can't do any harm testing.
Me.Name means get the name for the object I'm in (code-wise).

[Beany]

sorry it didnt work im getting the following error message:

Run-time error '2530':

The SelectObject method can't be used on a report that is currently printing

[Beany]

this is my last problem..................................

i need help

[NeoPa]

this is my last problem..................................

i need help

See post #3 Beany. I suspect this is where we've got to on this.
We cannot tell you what you may or may not have in your current code.
This is something you'll have to find for yourself I'm afraid.

[twinnyfo]

Beany,

I used that same code on reports for months and then Access all of a sudden decided to start giving me the same error you described. Here is the solution:

From the parent form that calls your report:

    DoCmd.OpenReport "ReportName", acViewPreview
    DoCmd.SelectObject acReport, "ReportName"

For some reason, this allows the report to complete its opening procedures and then allows you to select it. It should come to the front (if all your other forms' modal and popup properties are set to no.

Even if those forms are set to modal, you can add a few lines of code to your form to set modal to false, then open the report. Then, in the OnClose event of your report, reset the modal porperty on your forms to true.

Good luck!

[NeoPa]

Beany:
Run-time error '2530':

The SelectObject method can't be used on a report that is currently printing

Wow. This thread is from my first month of involvement with Bytes (or TheScripts as it was called then).

@Twinnyfo
If you look back through the thread you'll see that your (very sensible) suggestion has already been posted, but to no avail (See quoted post for reported results of that).

Now I go through it again all this time later, I notice that this error message indicates that the report is not being opened as one would suspect (and as Twinnyfo had it) with the acViewPreview parameter value, but clearly it must have used the default of acNormal instead, which causes the report to print directly to the printer instead of to show on the screen. This is the cause of the problem, but as the OP (Beany) posted the question so poorly (without including any hint of their code) that never came to light before.