As a 'user' of the Advantage DB (local server only) I was wondering, why
the type names SQL_Double, SQL_Integer, etc. are used in CASE/CONVERT statements instead of the 'normal'
type names like 'float' and 'integer', which are already used in the declare
statements and the create tabel statements?

If it's backwards compatibility, why not allow the SQL_ types AND the
'normal' types, which are used in ADS already?

This would be less confusing for developers to 'use' the ADS sql-syntax.

Delphi XE2 introduced a new dbExpress driver that permits dbExpress to use ODBC drivers. In order to use this dbExpress driver successfully with the ADS ODBC driver, it is necessary to set the RowSetSize parameter to 1 (instead of the default 20). Without this change, the ADS ODBC driver only returns a single record. (Thank you to Edgar Sherman who discovered this configuration issue.)

The Delphi IDE has a feature called Data Explorer, which uses dbExpress drivers to permit you to open tables, views, and stored procedures, examine metadata, and execute SQL statements. However, due to the RowSetSize parameter issue, which cannot be configured for the Data Explorer, the ADS ODBC driver returns only a single record when attempting to view tables. I would like to see the ADS ODBC driver default change in such a way that changing the RowSetSize parameter is unnecessary, which should enable our use of the ADS ODBC driver in the Data Explorer.

As a 'user' of the Advantage DB (local server only) I was wondering, why
the type names SQL_Double, SQL_Integer, etc. are used in CAST/CONVERT statements instead of the 'normal'
type names like 'float' and 'integer', which are already used in the declare
statements and the create tabel statements?

If it's backwards compatibility, why not allow the SQL_ types AND the
'normal' types, which are used in ADS already?

This would be less confusing for developers to 'use' the ADS sql-syntax.

Currently the backup takes far too long to backup a database with no connected users. Windows file copy can accomplish a 2.2GB file copy in less than 2 minutes versus a 26 minute advantage live backup. The windows file copy runs the risk of corrupt files unless you turn off the advantage service before proceeding (not an option with multiple databases on the server).

Assume a fieldname like "CustomerId"
It is likely this field is used in many tables.
If the datatype of such field is changed from integer to numeric (just an example), the change of fieldtype should occur in all tables with the same fieldname. (Maybe a list of tables and "Are you sure" might be usefull).

In Data Architect, When selected a table, and when scroll through in list box "Order by", add a facility to display the Index Key. Currently key shows only when a tag is selected. If you have 20 tags, you have to select each tag to find the index key you are looking for.

Ads.ini (at least as of ADS 9.10.0.23) is still being stored in the %WINDIR% (C:\Windows). This fails under Win7/2008, especially with limited rights users (but even with admins). The file is actually saved if modified after install in a virtualized folder, meaning that after logout all settings are reset to the original ones.

The first example:
...
AdsConnection1.IsConnected := True;
...

Then look "Database info" on Advantage Configuration Utility:

Work areas: 1
Tables: 1

Ok, then:
..
AdsTable1.Open;
...

Database info:

Work areas: 2
Tables: 2

Ok, now close AdsTable1:

..
AdsTable1.Close;
...

Database info:

Work areas: 1
Tables: 1

All correctly! But with AdsQuery problem..
Example:

...
AdsQuery1.SQL.Text:='select * from table1';
AdsQuery1.Open;
...

Database info:

Work areas: 3
Tables: 2

Ok, now close AdsQuery1:

...
AdsQuery1.Close;
...

Database info:

Work areas: 3
Tables: 2

Why not close the connection to table1?
How to do it force?

Currently, when restoring a database backup to an empty folder, ADS logs to its error log file 3 and 4 errors for each ADT and ADI file restored (file not found type errors). This rapidly fills up the ads error log with false errors. Add option to indicate that we are restoring to an empty folder and only log an error if the file already exists. (Kinda of strange anyway, logs error if old file doesn't exist, but doesn't log error if it is wipping out an old file and its data).