Make form visible from VBA code

[GraeagleBill]

I have an app whose startup module opens a form thus:



DoCmd.OpenForm "frmLinkCntl", , , , , acHidden

Form "frmLinkCntl" in turn opens another form "Addrlst-II". Form "Addrlst-II" has a command button whose click event attempts to make form "frmLinkCntl" visable before closing "Addrlst-II".

The statement attempting to make "frmLinkCntl" visible fails. I assume because I've not code the "Forms" statement correctly?

Forms("frmLinkCntl")!Form.Visible = True

I get this error:

[June7]

Try:

Forms("frmLinkCntl").Visible = True

[GraeagleBill]

Forms("frmLinkCntl").Visible = True

Gets me error:

[June7]

The code works for me.

If you want to provide db for analysis, follow instructions at bottom of my post.

[GraeagleBill]

June,
I'll have access to a ACCESS 2010 system in the AM and will compile there to see if I can have the same success that you've had. ACCESS 2003 has a historical problematic issue with the use of acHIDDEN used with DoCmd.OpenForm so maybe I've bumped my head against that.
Bill

[amrut]

From the error code I think the form you are trying to unhide is CLOSED.

[GraeagleBill]

June, my app fails the same way with A2010 as it does in A2003. Rather than bother you with sending the app, I decided on a different approach.

You'll recall, and perhaps other followers of this thread will as well, that this all started with my post regarding the problem with the query wherein I was attempting to JOIN fields from two tables where the tables WERE NOT stored in the SAME back-end mdb. (Query Forum Post: "Syntax error in From clause") Following the URL you posted there, wherein Albert and Dirk posted code to both check for and delete a linked table, I'll use that code to switch a table link from one back-end mdb to another.

In my app, the form "Addrlst-II" has as its RecordSource a query based on the table "Addrlst". With that, one MUST CLOSE the form "Addrlst-II" if the table it's bound to is to be changed from one back-end to another. I have not yet employed Albert's and Dirk's code yet, but I've successfully implemented code to deal with the closing of "Addrlst-II" and opening of another form to interface with the user's choice of a different table source, followed by a re-opening of "Addrlst-II". That form's code module will attend to the re-linking of table "Addrlst".

Thanks for your help and the time others spent on this thread,
Bill