Opening form B from form A does NOT close form A - why ?

[ksor]

I have a form showing a textbox with different names of persons - 2-clicking on one of the names shold:

1) CLOSE THE CURRENT FORM
2) Open another form showing that person from the 2-click

I use this code in the 2-click event of the textbox

Dim f As Form, rst As DAO.Recordset
DoCmd.Close acForm, Me.Name
If CurrentProject.AllForms("PERSON Vedligehold af").IsLoaded Then
Set f = Forms("PERSON Vedligehold af")
Set rst = f.Recordset.Clone
rst.FindFirst "[PersonID] = " & Me.PersonID
f.Bookmark = rst.Bookmark
Set f = Nothing
Set rst = Nothing
Else
DoCmd.OpenForm "PERSON Vedligehold af", , , "PersonID = " & PersonID
End If

And it works nicely EXCEPT the first form is still open !



What do I do wrong ?

[aytee111]

Why do you want to close the form? It adds complexity to your process. Otherwise, close the form as the last thing, not the first.

[Bulzie]

You need to close the first form in the OnOpen event of the 2nd form.

[ranman256]

it doesnt have to.

[ksor]

It doesn't work - the form that SHOULD BE close remains open - argh !

[Micron]

I tried something similar to what you have and can't replicate the issue even without moving the close method to the end of the code. Putting it early is a mistake AFAIC, because it will cause execution to branch off the current procedure into the close event for the very form you want to continue running code on. I figure it's cancelling itself, but that doesn't make sense. But "it doesn't work" doesn't help much. What "doesn't work"? Putting the call to close in the second form? Maybe post a zipped copy of your db?

[HiTechCoach]

In my experience with Access since 2.0, if a form opens a recordset then it must remain open until the recordset is closed.

I use some very similar code but I have it in a standard VBA Module. Not in code behind the form.

Here are the basic steps I use:

1) hide the current form
2) call the function to open the next form
3) close the form


This may help:

MS Access – VBA – Requery a Form While Remaining on the Same Record

[ksor]

Yeah, I too have experienced that hide/show is a better method.

My situation is, that I want to open forms in 3 levels on top of the main menu and then go back and forth between these levels.

Hide/show seem to be a much easier and better method to use then.

I'm now working on some generalized method for this hiding/showing different forms.

[HiTechCoach]

My situation is, that I want to open forms in 3 levels on top of the main menu and then go back and forth between these levels.

Hide/show seem to be a much easier and better method to use then.

By hiding/showing a form, you also save the overhead of load time.

Another approach I use is a tab control. You navigate between the pages of the tab control. Check out this example: Wizard Form template

[Bulzie]

Couple ideas. Does the 2nd form have to remain open? Once you select a name and 2nd form opens, can they do whatever they need and then close that 2nd form(model/popup)? Or if not, can you add 2nd form as a subform to your first form? Just seems overly complicated to have to know which forms are open and such.

And an alternate way, Open Form 2 (or if it is open already) and using code on Form2 and the PersonID field from Form1, set the RecordSource as needed in Form2, then close Form 1. So do it all in Form2, not Form1. Only thing in Form1 is Opening Form2.

[ksor]

Thx to all of you ... I'm working on the project ;-))

[ksor]

I now made a solution where I from the MAIN MENU with buttens can OPEN my forms and then they STAY open but will be hidden when "close".

It works very nice and have the side effect that data in the forms stay the same while using other forms - that's a great increase in functionality in my case.

In some remote corner of the main menu I have a counter showing the number of opened (and now hidden) forms - just for checking - nice !

I can recommend that "Open and then hide" idea - works very nice !

[HiTechCoach]

Glad to hear that it worked for you. It is a trick I have been using for over 15 years in Access.

Thanks for paying it forward by sharing your solution.