And of course with these SQL queries, you are losing the ability to open the scenario directly by clicking on the result line, since you have
renamed the key field(s) the click-code relies upon to find scenario number. (Here you have renamed ScenID as ScenarioID for example).
Not a major issue, but some end user will likely try to click the result, get an error message and come on here to complain.
The required field for each of the 2 tables used is detailed in the Game Guide section on SQL usage in Scenhack. The field name is different in each table - someone may well try an SQL query that combines the 2 tables. Each of the 2 SQL-using tabs queries a separate table, but the tables are both open globally - I have run queries in both panels just fine.
There
is a Microsoft help file for the Borland SQL but it is not included as it's proprietary, and also since vista or 7, Microsoft Windows refuses to read the old Windows help file format
. So any queries on what Borland Paradox SQL keywords are, should be done with a google search to find whoever owns Borland these days own help pages. The below looks like it is relevant:
http://www.nknabe.dk/localsql/index.html