Add a "No fields selected" warning

Tomsie

I know it's always worked like this, but if a novice user doesn't select any fields in the Query Designer then an "OK" just offloads to the SQL engine with a badly formed bit of SQL and gives an "Invalid SQL Statement" error, which the user then finds baffling. Any chance that a bit more checking could be done? Apart from if the user is intervening in crafting their own coded calculation fields it shouldn't be possible to create exception instances from this user interface, should it?

TIA, Paul

nicocizik

Hi Paul,

The Query Designer was designed to give advanced users direct access to the database. Therefore all errors returned are errors returned directly from the database (some better than others). The Query Wizard was designed with a more "friendly" experience in mind.

I understand what you are saying though. Generally DB errors can be ambiguous and unhelpful. We will see about improving the error given when no fields are selected in the Query Designer for a later release.