Opening Dayasheet Form acDialog doesl not halt code excecution

[Middlemarch]

DoCmd.OpenForm "Form1", View:=acNormal, WindowMode:=acDialog
Stop

Stop does not execute until I close the Form

But this fails. Stop executes immediately

DoCmd.OpenForm "Form1", View:=acFormDS, WindowMode:=acDialog
Stop

Is this correct? Is there anyway for a Datasheet form halt code until closed ?

[June7]

Code execution of main form is suspended with the acDialog parameter. The second form must close then main form code resumes execution.

What do you expect? Why are you trying to use Stop? Exactly what are you trying to stop?

[Bob Fitz]

Code execution of main form is suspended with the acDialog parameter. The second form must close then main form code resumes execution.

What do you expect? Why are you trying to use Stop? Exactly what are you trying to stop?

But that doesn't seem to be the case if the form is opened in datasheet view

[Micron]

This is how I understand it:
You can't switch a popup form from form view to any other view, even with code, and a form isn't a popup in design or datasheet view. So my guess is that by using datasheet view, you over-ride the modal effect. That would be because acDialog sets the popup and modal properties to True. If you can't set both to true, my guess is that acDialog doesn't work but the form or code doesn't complain either.

[Bob Fitz]

... my guess is that acDialog doesn't work but the form or code doesn't complain either.

If acDialog doesn't work would you consider that to be a fault/bug?

[Micron]

I think so. I mean, shouldn't the vbe compiler at least mention that the dialog parameter isn't compatible with the form view chosen?
Don't forget that what I said is a guess, based on the documentation saying (at least how I interpret it) datasheets can't be popups and that acDialog sets modal and popup properties. The fact that the code doesn't wait for the "modal" form seems to suggest that. I would try it this way to see if it makes any difference, but don't expect the same results if you open the form from the nav pane:

DoCmd.OpenForm "Form1",acFormDS,,,,acDialog

Apparently, that worked 15 years ago, but the documentation is much more recent so I don't hold out a lot of hope for that working.

EDIT - I think the common solution to the problem has been to make the form continuous but look like a datasheet.

[June7]

Okay, learned something new. I've never used acDialog with form in datasheet view.

[Bob Fitz]

Okay, learned something new.

Me too. Trouble is I seldom remember anything now that I'm old

I've never used acDialog with form in datasheet view.

It would appear that nobody has . Well not with any success

[Middlemarch]

Interesting. I used datasheet mode as there's multiple records and I want to to select one of them. Maybe a continuous Form would work but I've never used one or seen how its designed.
Is this perhaps something to try ?

DoCmd.OpenForm "Form1", View:=acFormDS
do
do events
loop until "Form1 closes"
stop

I don't yet has a routine to detect if the Form1 is closed or not.
@June asked what the Stop is For? To stop the code so I can test/see its working.
Isn't modal to force the Form to be closed. Does that stop code the same way as acDialog for non-datasheet Forms ?

[June7]

I should have said "I never tried to use acDialog with a Datasheet form."

Make a continuous form look like datasheet by positioning textboxes and comboboxes against each other and minimizing height of Detail section.

Lose ability to manually adjust width of columns because there aren't any.

[isladogs]

OK ... second bit of strange behaviour I've experienced today
I've just tried opening a datasheet form using acDialog in both A2010 & A365 and got this result



The tiny form that appeared couldn't be enlarged. All I could do was close it!

[June7]

Test with form that is set as Datasheet for DefaultView.

DoCmd.OpenForm "Games", , , , , acDialog

Form opens displaying a single record in Datasheet

DoCmd.OpenForm "Games", acFormDS, , , , acDialog

Form opens displaying all records in Datasheet.

And when form is not set as Datasheet in DefaultView, form opens just fine when using acFormDS and acDialog.

I confirm that if DefaultView is set to Datasheet and/or acFormDS is used, acDialog is ignored.

[Micron]

when form is not set as Datasheet in DefaultView, form opens just fine when using acFormDS and acDialog.

In that case is 'acDialog ignored', which I take to mean that code doesn't halt because it doesn't behave as a modal form?
Thanks for doing that testing, BTW.

[Bob Fitz]

OK ... second bit of strange behaviour I've experienced today
I've just tried opening a datasheet form using acDialog in both A2010 & A365 and got this result



The tiny form that appeared couldn't be enlarged. All I could do was close it!

Yes I got that when I was playing around with it yesterday but, as I'm sure you'll already know, using: Docmd.Restore as the next line after the line that opens the form, will give a useable form. Yet another indication that the acDialog does not work.

[Middlemarch]

Very nice of everyone to offer ideas. I have found I can simulate acDialog for a data sheet Form as in Msg #9.

DoCmd.OpenForm "Form1", acFormDS
  Do
  DoEvents
  Loop Until CurrentProject.AllForms("Form1").IsLoaded = False

This allows click events in Form1 to be used.
I didn't add acDialog as it has no effect