Prevent sorting of data in a form

[dhstein]

I have a form based on a query. The form is a display for information
purposes only. The order of the data is important, so I want to prevent any
sorting of the records. I restricted edits but I'm not sure how to restrict
sorting. Possibly this should be a report - but I like the continuous
display that the form allow. Can a report display the same way? Thanks for
any help on this.

 

[KARL DEWEY]

The order of the data is important, so I want to prevent any sorting of the
records.
This is contradictory to say not sorting but order is important. If you do
not sort the query it will not be sorted.
You can add a field for special sort of your own like A,D,C,B,E,F,I,H,G, etc.

 

[dhstein]

Thanks for the response Karl. The order is important - which is why the
query produces the information in a very specific order (the query is sorted)
- and the form represents the data in the same order. I want to display it
that way and not allow the user to change the order of the data.

 

[ken]

I think you must be referring to the ability to sort a form by means
of the A-Z or Z-A buttons on the toolbar. These set the form's
OrderBy and OrderByOn properties, which will override the ORDER BY
clause of the underlying query. In fact a query itself can,
surprisingly, have its ORDER BY clause overridden in the same way. If
you put:

Me.OrderByOn = False

in the form's Current event procedure this will go some way to
stopping a user from imposing a sort order on the records as, while
the form will be sorted n the field the user selects to order the
records by, it will revert to the query's sort order once they
navigate to another record, moving the record pointer to the first
record in the query's sort order. This is not a very satisfactory
solution, however, and it would be better to deny users access to this
facility by using a custom menu and toolbar for the form, excluding
the relevant menu items and buttons.

Ken Sheridan
Stafford, England

 

[Ron2006]

The other consideration is that if the application is split as it
ought to be, then IF the user gets a fresh copy of the application
each time then it will also revert to the original design sequence.

Also if you set the order in the on open event of the (sub)form, I
believe that will also reset it every time the form is opened, even if
they do not get a new version each time they execute.