A lot to discuss here...
Are wizards in the future for 9 or are we going to have to become our own SQL wizards?
There are very many wizards already there, in the form of transform templates where you can click the "edit query" button to have it write SQL for you (very wizardly...).
If you prefer something more free-form than the SQL the system writes for a template, use the query builder.
I need to have meaningful labels for the areas in my map.
Labels are still at Radian level, not where they are going. Keep your finger on the pulse of changes with Future. As formatting adds labels there will be far, far more capabilities with labels.
I have to have the correct information in the table fields. When I opened the 8 map file the fields on the related table did not come through. So now I need to figure out how to relate the area table with the data table. Again, the wizard in 8 makes it easy to relate the table to the drawing.
I don't quite follow the above but in general Radian / Future / 9 has far more capabilities than 8. There is no such thing, by the way, as an "area table" that is different from a "data table," so I don't understand what you mean by that. Everything is a table. A drawing is a viewport into a table. If there are any fields you can work with in a query using a drawing's name, those fields are in that drawing's table.
Also in 8 it is easy to update the calculated fields in the table. I don't see how to update it in Future.
Future automatically updates computed fields. I note that "calculated field" is not Manifold terminology. The right term is "computed field." Use the precise terminology so you can follow along with examples and report exactly what you've done in the forum.
You can add a field that has set field values, and you can do something related, but different, which is to add a computed field. There are two examples that show the difference:
Add a field to a table and fill it
Add a computed field to a table
If you just added a field to a table and filled it, but did not create a computed field, well, there is nothing to update because you've just filled that field with static values, not computed values. It's an ordinary field and will have white background. If you created a computed field as set forth in the second topic above the field will have a light gray background because it is not editable... the values in there are computed based upon some expression.
Is there a way to save queries to the Project pane?
Queries you create in the project pane are automatically saved. See the "to create a query" list of instructions at the very top of the Queries topic.
Do you mean, is there a way to save a temporary query that I wrote in the Command window into a query component in the project pane? Yes, of course:
Copy the query text. Create a new query in the project pane using whatever name you like. Open that query and paste the query text into that query. Done. As noted in the Queries topic changes made to query components are automatically saved.
As advised in the Queries topic, the usual way to create a new query is to create a new query in the project pane, to open the query and then to go forth and write whatever SQL you want in that query. But if you didn't do that but instead just launched the Command Window in an ad hoc way, no problem. Copy whatever SQL you've written and paste it into a query component.
How can I reuse queries from Manifold 8? They need to link to a table.
Open the query text and re-write it for Radian SQL. Depending on the query that can be trivial or it can be significant.
They need to link to a table.
Not sure what you mean by the above, as queries are operations on tables, so they all link to a table. Could you describe with more detail what you had in mind?