Datasheet or Continuous Form

[MattBaldry]

Hello again forumers,

Is there any benefit/difference to having a continuous form layout vs a datasheet layout when having a subform form sales order/purchase order items?

At the moment I do the datasheet option, and it works fine. I just wondered if there were any discernible benefits to changing these to a continuous form that then looks like a datasheet.

~Matt

 

[isladogs]

Mainly personal preference.
Continuous forms allow greater flexibility in terms of appearance and the layout can be locked down to prevent end users modifying it.
Datasheets are quicker to implement and give users the opportunity to change items such as column order and to hide columns. However, their appearance cannot be modified as much

 

[MattBaldry]

Mainly personal preference.
Continuous forms allow greater flexibility in terms of appearance and the layout can be locked down to prevent end users modifying it.
Datasheets are quicker to implement and give users the opportunity to change items such as column order and to hide columns. However, their appearance cannot be modified as much

Thanks Colin.

I assume that with a continuous form layout you could have "sort" buttons above each column. Would this be something easy to code, have you any experience with this?

~Matt

 

[isladogs]

I have indeed. Have a look at my Student Target Group Explorer example app in this thread.
https://www.access-programmers.co.uk/forums/showthread.php?t=302189
It has sort buttons on each column header plus a small up/down arrow to indicate whether the sort is ascending or descending.

 

[MajP]

I usually use Colin's approach, but recently someone asked about using the built in features to mimic Excel sort and filter. I was surprised how well it worked and very easy to implement.

 

[isladogs]

MajP
I'd forgotten about that method which does indeed work well and, as you say, needs remarkably little code
If you haven't already done so, I think it would be a worthy example database with a brief explanation of the code in the accompanying thread.

 

[apr pillai]

I have tried some simple tricks with the Datasheet View of the Form: Event Trapping Summary on Datasheet Form.

 

[Gasman]

MajP
I'd forgotten about that method which does indeed work well and, as you say, needs remarkably little code
If you haven't already done so, I think it would be a worthy example database with a brief explanation of the code in the accompanying thread.

It needs supporting picture files I believe, as I received an error

cmd.Picture = "Filter"

when setting a filter?

 

[isladogs]

That code just sets the picture on the selected button to either a down arrow or a filter image. The images are located in the Image Gallery

IIRC that feature doesn't work in A2007. That section of MajP's app uses the same idea as the button image code on my Student Target Grade Explorer app for which I provided a separate version for A2007.
See http://www.mendipdatasystems.co.uk/multiple-group-filter/4594454290

Try disabling that section of code and it should work for you in A2007