I'd like to be able to do an alter table on a live data set. No exclusive access for ALTER TABLE.

I would like to have a UpdateObject for a Query, so I can define the sql for update/Insert for a TADSQuery. this would avoid to make such things with Triggers

It would be fine when the AOF (of a TADSTable) could have the same Syntax like the SQL-Where-Part of a TADSQuery.

Typically ADS will not consume too much of the system resources so as to allow other processes on the system enough resources to run properly. However, if the system was dedicated to ADS, it would be nice to configure ADS to be more selfish with resources to improve performance.

When an 'ORDER BY' clause exists, this sort order should remain until a new query is posted. Edited data should not be resorted immediately after posting a record - this behaviour interferes manual record changing (e.g. when copying a field value to the next record in the query result set).
This issue should be solved at least for temporary indexes with 'ORDER BY' by introducing an Option 'Fixed' for those indexes or, even better, making this the default behaviour (like MySQL etc.).

Make last statement in stored proc be the result, no need to populate output table.

The ability to generate a SQL dump of the entire database (minus blobs etc) from the server would be an excellent backup option.

This would allow for an executable to be deployed that uses the TDataSet Descendant components but that does not requiring the ACE DLLs. Usefull if exe is supporting multiple databases.

Details (e.g., username, password, connection string) should be command-line parameters while SQL statements should come from stdin. That way I could either use it with a command-line prompt or redirect into it from .sql text files with scripts.

Built in lookup fields for tables. User specifies source table, key field, etc. A writable dataset, but ignore updates to the lookup fields. Or some mechanism to make static cursors live in more situations, where we can make better decisions and try to resolve user record updates automatically.

Most ADS error messages dealing with table problems (7000 series) do not include much information. Would be nice to have other data included such as table name, record number, field name, etc, depending on the type of error.

When processing data in a stored procedure or script using a while loop in order to report the real progress of the actual script instead of getting progress on each query execution. See example below.

DECLARE Query cursor;

OPEN Query as select * from SYSTEM.TABLES; WHILE FETCH Query DO

--Update Statement 1

--Update Statement 2

--Manually Increment Progress Callback

END WHILE;

Many databases support an enumerated field type. It would be useful to be able to assign an Enumerated value, instead of storing numbers that translate to the selections.

i.e.
CREATE TABLE Info (
Relationship ENUM('self', 'spouse', 'guardian', 'other')
);

On DBF table open, check table structure vs data dictionary structure definition and adjust dictionary definition if different.

My request would be to provide the same functionality that SQL Anywhere is working in beta right now...

The ability to send email alerts warning of Bad Things Happening to your "SQL Anywhere" database server is the release-defining feature of the new SQL Anywhere Server Monitor now available in beta.

The monitor lets you pick and choose what you want to be warned about and also set values for each metric:
- CPU Usage
- Memory Usage
- Disk Usage
- Connections being blocked
- Connection count
- Long running queries

Would be useful to have a scalar function that returns the OS user login name, rather than the dictionary user name which is what USER() returns for dictionary connections. Perhaps add an option to the USER() scalar to alter its behavior in this way.

normal PHP driver are "ads_....()" funktions.

To generate portable PHP5 programs it's much better to use PHP data objects (PDO)