Why is sorting in the database view bad? (Form Properties > Datasheet View)

Why would one not want to sort records in a form using Form Properties[color=blue]
> Datasheet View > Sort Ascending?[/color]

It's the fastest way, isn't it?

<sierrachang@gmail.com> wrote in message
news:1130340930.933763.38030@g43g2000cwa.googlegro ups.com...[color=blue]
> Why would one not want to sort records in a form using Form Properties[color=green]
>> Datasheet View > Sort Ascending?[/color]
>
> It's the fastest way, isn't it?[/color]

No, the fastest way would be to sort in the Query or SQL you use as Record
Source for the Form, I suspect. I don't give the users "datasheet view" in
the database applications I prepare, because there are so many things that a
user can (inadvertently) do that will cause trouble.

Generally, datasheet view is useful for end-users, not for developed
application and the "Windows Way" is to let the user have control of their
own desktop unless there is compelling reason to not do so. I can't think of
a compelling reason not to allow this, if it is what the user wants to do.

Larry Linson
Microsoft Access MVP

Larry Linson
Microsoft Access MVP

It converts the underlying query to DISTINCT, so you
may have a different number of records after sorting.

(david)

<sierrachang@gmail.com> wrote in message
news:1130340930.933763.38030@g43g2000cwa.googlegro ups.com...[color=blue]
> Why would one not want to sort records in a form using Form Properties[color=green]
>> Datasheet View > Sort Ascending?[/color]
>
> It's the fastest way, isn't it?
>[/color]