Double-click in subform to open child form

[2myle]

Hello experts,

Sorry, this is probably a newbie-question...

I have a form for customer details, which includes a subform (datasheet, multiple columns) that lists the orders that correspond to that customer.

On the subform, I would like to define a double click event that opens a separate form with all details of a specific order (depending on the row in the subform on which the user double-clicked).

But I don't know what I should define the double-click event on. Should I define a double-click on each field (i.e. column)? Or is there an object for the entire row?

Your help would be greatly appreciated.

[Scott Price]

Hello experts,

Sorry, this is probably a newbie-question...

I have a form for customer details, which includes a subform (datasheet, multiple columns) that lists the orders that correspond to that customer.

On the subform, I would like to define a double click event that opens a separate form with all details of a specific order (depending on the row in the subform on which the user double-clicked).

But I don't know what I should define the double-click event on. Should I define a double-click on each field (i.e. column)? Or is there an object for the entire row?

Your help would be greatly appreciated.

I think you'll be better off either changing your subform to a listbox using the same record source (listboxes recognize clicks, doubleclicks etc.) or to continuous form view instead of datasheet view. Continuous form view emulates (looks similar to) datasheet view, but allows also the click, doubleclick etc events. As far as I know datasheet view doesn't recognize those events.

The way I have done what you want to do before is to place a command button in continuous form view at the right of the record that opens the detail form on it's click event. It's fairly simple then to open the detail form using the OrderID number as the openargs setting to direct your order details form to the particular order you want to edit. (the idea with the command button instead of double click event is documenting the process for new users of your database, i.e. how are you going to tell them that doubleclicking on the field does anything? Not an impossible thing to do, just one that involves more work than simply placing an order details command button adjacent to the order record.)

Regards,
Scott

[2myle]

Thanks Scott,

I hadn't realized you could add buttons to continuous form views. That is indeed a more elegant solution for what I wanted to do, it's already working.

Not that the "new user" argument is a big concern to me; my wife is my only customer... ;-)

Muchas gracias,

Erik

[Scott Price]

Thanks Scott,

I hadn't realized you could add buttons to continuous form views. That is indeed a more elegant solution for what I wanted to do, it's already working.

Not that the "new user" argument is a big concern to me; my wife is my only customer... ;-)

Muchas gracias,

Erik

De nada, Erik...

Glad to help! Glad you got it working, too... You're lucky that your only customer is your wife :-) End users can come up with remarkably clever ways to get into trouble with something that to the developer thinks is as simple as 1 2 3!!

Regards,
Scott