acDialog in Openform not working with acFormDS

[Leif]

I would like to open a form and wait for the form to close before continuing
execution in the code the does the open form. That works fine in the default
setting such as:

DoCmd.OpenForm "ProjectManager", , , , , acDialog

However, if you want the form to open up in datasheet view, like:

DoCmd.OpenForm "BPProjectManager", acFormDS, , , , acDialog

then, for some reason, VB does not wait, but continues execution, despite
the acDialog.

Has anyone experienced this problem? Is there a work-around?

Thanks,
Leif

 

[Ken Snell \(MVP\)]

Datasheet view cannot be opend in dialog mode.

 

[Leif]

Seems random. Is there a work-around?

Datasheet view cannot be opend in dialog mode.

 

[J_Goddard via AccessMonster.com]

Hi -

You could try using the datasheet form as a subform to a regular one which is
opened in dialog mode. A little clumsy, perhaps, but it works - I use that
technique.

John

Seems random. Is there a work-around?

Datasheet view cannot be opend in dialog mode.

[quoted text clipped - 17 lines]

 

[Ken Snell \(MVP\)]

Design a form set to Continous Forms View that looks like a datasheet view
(controls right next to each other in columnar format), and then open that
form in dialog mode.

 

[David W. Fenton]

Design a form set to Continous Forms View that looks like a
datasheet view (controls right next to each other in columnar
format), and then open that form in dialog mode.

Except that it's *not* a datasheet, which means:

1. tab order is rigid, as opposed to being able to use the arrows to
move in any of the four directions in the grid

2. columns can't be resized.

No, the real solution is to embed the datasheet as a subform in an
empty form that is opened as a dialog.

 

[Ken Snell \(MVP\)]

news:[email protected]:

No, the real solution is to embed the datasheet as a subform in an
empty form that is opened as a dialog.

Depends upon whether you want something that looks like a datasheet or is a
datasheet < s >.

 

[David W. Fenton]

Depends upon whether you want something that looks like a
datasheet or is a datasheet < s >.

I would say it depends on whether you want something that *works*
like a datasheet or not. If it looks like a datasheet and users are
accustomed to working with the features datasheets provide and that
continuous forms lack, then it will frustrate them.

The replacement for a datasheet is a datasheet, not a continuous
form. It a continuous form were satisfactory in the first place, why
use a datasheet at all?