can't sort my query with the AZ and ZA button

[eyoung]

Two of us are sharing a MS DB...if we create duplicate queries, she has
the sort option and I do not...my little "AZ-->" and "ZA -->" buttons
are grayed out. Why is this and how can I get the sort to work for me?

I have tried to right click the top of the query window, choose "Apply
Filter/Sort" but get a message that the records are locked...tried it
just becasue I don't see anything else that remotly looks to be helpful.

 

[aaron.kempf]

the problem is that MDB sometimes shuts down the ability to sort.

MDB is a flaky-ass platform.

spit on anyone that still uses Access MDB.

Access Data Projects are the way to go; they sure never have this
problem


-Aaron
ADP Nationalist

 

[eyoung]

Thank you but this does not answer my question...

 

[John Vinson]

Two of us are sharing a MS DB...if we create duplicate queries, she has
the sort option and I do not...my little "AZ-->" and "ZA -->" buttons
are grayed out. Why is this and how can I get the sort to work for me?

I have tried to right click the top of the query window, choose "Apply
Filter/Sort" but get a message that the records are locked...tried it
just becasue I don't see anything else that remotly looks to be helpful.

I suspect the problem is that you are sharing the same database.
Consider using the "Database Splitter Wizard" to split the database
into a "backend" - containing just the data tables - and a "frontend"
containing the Queries, Forms, Reports etc. Each of you should have
your own copy of the frontend, linked to the tables in the backend.
This will prevent this type of error; as it is, you can't change the
nature of the Query because that would interfere with your coworker's
use of the Query! You surely wouldn't want the query you're using to
suddenly and unexpectedly reverse its sort order, would you??

John W. Vinson[MVP]

 

[aaron.kempf]

Access MDB randomly decides that a query is 'too complex' and it just
flat out craps out and it won't let you sort.

the fact that you're always dealing with work-arounds in MDB?
it's laughable.

get a real database and lose the training wheels