First, you don't save calculated fields in a table. If you are, tell me the real good reason you may think you have.
If you make a query and create a calculated column, then after you run the query to get a recordset you can click on the column heading of the calculated field and use the A-Z button.
Now don't misunderstand me. You can do the calculation on the form OR within the query Or report. But as you'll see, if the calculation is in the query, you can easily sort the recordset on it. Either way you do the calculation, query or form, there's no reason to store it in a table. Unless all the fields in the calculation process will be static forever, which is quite rare.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.