advantage on UserVoice

Data Architect: correct bug in using two monitors and wide window?

2012-05-15T09:38:22-07:00

Anonymous suggested:
When stretching out the Data Architect window, it can be useful for looking at several files. However, whenever I call up a new table to look at, it is always placed to the left of all other tables, making the size even larger and requir=ing me to use the scroll bar below to look at it. No need to stretch out the window even wider when a table is opened.

Connection Shared Locking of Datasets

2012-04-27T07:36:25-07:00

Paul Henke suggested:
There are two lock states for a dataset right now: locked and not locked. If you open an ADS connection and start a transaction then you get ADS handles for each table you open. But if the table is closed and another following process in the same transaction needs to alter the same dataset again you get a new ADS handle for the table - in fact you are opening a new table and in this case the dataset is still locked by the closed table. On the TAdsQuery side you can perform multiple operations on the same dataset within one transaction, why are you not able to do that with TAdsConnections and TAdsTables?

Same Syntax for AOF and SQL-Where (LIKE, IN, ...) [updated]

2012-04-27T07:33:06-07:00

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

Clemens Maier, Dontenwill AG said:

We would also need the counterpart: In our ERP-Application, users can define "read permissions" as AOF-Filters for every table in the dictionary.

To be able to use the same filters in SQL based request, we would need a SQL function like "AOF(SQL_ALIAS, AOF_FILTER_STRING)"

Add Option to treat NULL as Default value.

2012-04-21T07:09:10-07:00

raoul suggested:
So I dont have to wrap each field with IFNULL(). Crystal Reports has this option and works hwne using ADS.

Need ability to kick users preventing exclusive access [is now planned]

2012-04-20T12:40:11-07:00

Say you need to add a new field to a table and some jerk has the table locked and has gone off to lunch. Furthermore, you can't even tell WHICH jerk has the thing locked! Need better tools here.

Need ability to kick users preventing exclusive access [updated]

2012-04-20T12:40:03-07:00

Say you need to add a new field to a table and some jerk has the table locked and has gone off to lunch. Furthermore, you can't even tell WHICH jerk has the thing locked! Need better tools here.

mhagman said:

This ability will be in the ADS 11 Advantage Web Administrator utility.

Need ability to kick users preventing exclusive access

2012-04-20T11:31:40-07:00

Dan suggested:
Say you need to add a new field to a table and some jerk has the table locked and has gone off to lunch. Furthermore, you can't even tell WHICH jerk has the thing locked! Need better tools here.

autoinc [updated]

2012-04-20T11:28:33-07:00

Be able to specify an autoinc value.

Dan said:

How about the ability to RESET it - like you can do in SQL Server and Oracle?

ALTER TABLE on live dataset, no exclusive required [is now started]

2012-04-13T09:00:43-07:00

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

Make last statement in stored procedure be the result [updated]

2012-03-29T01:02:09-07:00

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

J. Mühlenhoff said:

When used from Delphi it would be very nice if you could do this:

Query.SQL.Text := 'EXECUTE PROCEDURE procname(...)';
Query.Open;

Possibility to keep deleted register in ADT format as CDX/NTX format table. This is main reazon I dont migrate from fox to adt format. [updated]

2012-03-28T12:30:02-07:00

Possibility to keep deleted register in ADT format as CDX/NTX format table. This is main reazon I dont migrate from fox to adt format.

Chris Franz {Sybase} said:

You seem to be commenting on the reuse of deleted records in our ADT format.

If you need to be able to recover any deleted records from a table I would recommend using a trigger to write deleted records to another table. This will preserve the records and also allow for the efficiency of record reuse.

There is an example of this type of trigger in Advantage Database Server: A developers guide, 2nd Edition

Possibility to keep deleted register in ADT format as CDX/NTX format table. This is main reazon I dont migrate from fox to adt format.

2012-03-28T09:40:34-07:00

Osvaldo L Aoki suggested:
Possibility to keep deleted register in ADT format as CDX/NTX format table. This is main reazon I dont migrate from fox to adt format.

Make ADSDOSIP work with Windows 7 [updated]

2012-03-28T09:06:07-07:00

It works with XP and Vista but not with Windows 7. ADSDOSIP.exe runs fine, but when we launch our DOS application, we keep getting DB CMD 1015 errors.

Osvaldo L Aoki said:

I have been problem using Windows 7 as cliente with windows server 2008 64 bits...It get error on creating dbf tables....

In Arc make it easy to visually differentiate null and empty fields. [updated]

2012-03-23T01:12:27-07:00

dean robinson said:

good suggestion. IS NULL, IFNULL etc don't work under some circumstances. we were forced to write our own stored function IsNullOrEmpty. nice to have a similar (reliable) one in the standard library?

Force ANSI character setting during installation [updated]

2012-03-23T01:08:31-07:00

The server installation currently allows ANSI character set as 'Default on machine'. This is unreliable for international users and should be made a mandatory selection, e.g. Engl(UK). Failure to do so results in incorrect SQL behaviour.

dean robinson said:

we second this. (it's unfortunate having to remember to select ANSI or instruct others to do so).

separate SQL help from the other stuff, and improve it

2012-03-23T00:36:13-07:00

dean robinson suggested:
would like ADS/ARC HELP to be better please. separate help for SQL so we know instantly which functions, keywords, expressions etc will work without so much reading small print, trial and error. Also more real world examples. ADS stored procs & functions for example are great but we had to do lots of R&D and googleing 3rd party articles to get them working properly.

NET STOP "Advantage" plus parameter to suppress warnings about connected users [is now declined]

2012-03-21T09:33:10-07:00

You can't use net stop in a batch file when this warming about any connected users pops up. All users should be forced to be disconnected.

NET STOP "Advantage" plus parameter to suppress warnings about connected users [updated]

2012-03-21T09:32:24-07:00

You can't use net stop in a batch file when this warming about any connected users pops up. All users should be forced to be disconnected.

mhagman said:

We agree this is a good idea however we don't think it is possible. The "net stop" command does not allow optional parameters after quickly researching and testing. Unfortunately, the "net stop" command is not and ADS command; but a Windows one.

However, we already have the SUPPRESS_MESSAGE_BOXES configuration option. If that is turned on, then those message boxes will not show.

http://devzone.advantagedatabase.com/dz/webhelp/Advantage10.1/index.html?master_suppress_message_boxes.htm

ftp

2012-03-10T06:07:43-08:00

Lucas suggested:
online backup to an ftp acoount

JDBC 4.0 compliant JDBC driver

2012-02-24T02:15:20-08:00

Anonymous suggested:
The current Advantage JDBC driver is JDBC 2.0 compliant only, so it lacks features like DataSource. "Certified for Java 1.3" is okay, but that was 12 years ago.

Better Support for Unicode with ADS tDataset Components

2012-02-16T00:25:36-08:00

MicrotronX suggested:
The tDataset Components for Delphi2010 and newer should support automatic detection of normal and/or unicode fields. We're having a applicaiton with more than 200 tables. Some customers want some fields to be unicode and some not. Its not possible to check this / react on these customer specific changes within the application. The best way should be an option within the tadsdataset component which should replace i.e. the tStringFields with tWideStringFields in runtime if needed and versus automatically I think, all needed changes to support unicode should be made within the tdataset components ... The application should support unicode automatically if the fields in dictionary are unicode.

Architect 10.10 - Can't edit a view when lockmode set to compatible [updated]

2012-01-26T12:31:54-08:00

Edgar Sherman said:

I believe this was fixed in 10.10.0.17

Fixed a 7028 error when modifying a view statement involving tables opened with compatibility locking.

Fire Triggers Using Compatible Not ADS Locking [updated]

2012-01-26T12:12:10-08:00

Based on testing I've discovered that when a trigger fires it uses ADS locking. This is fine if all tables involved with the trigger are ADT. However, this poses an issues if you're intent of the trigger is to insert data into a DBF to sync data between the two tables. I'm not sure why ADS locking is being forced because as far as I can tell, even if you attempt to force compatible locking when opening an ADT it still uses ADS locking anyway. So, using compatible locking should fix the the issue and allow to trigger into a DBF and still use ADS locking on ADT tables.

Edgar Sherman said:

This one confused me a bit as I thought it was already implemented so I wanted to clarify.
If there is a DBF table opened as compatible then the trigger will fire in compatible mode.
If there is a mix of ADT and DBF and the trigger is on the ADT, then the trigger will fire in proprietary mode / ADS Locking. If this trigger is meant to update a DBF open in compatible mode it will fail with a 7028 error

Enable the ADS ODBC driver within Delphi's Data Explorer

2012-01-25T05:35:21-08:00

Cary Jensen suggested:
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.

NUMA

2012-01-12T01:23:59-08:00

Elena suggested:
Add to support the optimizing ADS for NUMA technology?

Show Index key when scroll through Tags

2012-01-11T23:07:24-08:00

Kiron Joseph suggested:
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.

XE2 Support [is now completed]

2012-01-04T12:40:44-08:00

Support Embarcadero Delphi XE2

Add OUTPUT clause to Merge statement

2012-01-02T17:16:36-08:00

jon suggested:
just what the title says, ala Oracle, TSQL, etc Would preclude the need to create temp tables or a cursor to process Type 2 Dimension updates in a data warehouse (Kimball)

Suppport-System more Customer-friendly

2011-12-23T13:02:35-08:00

Günter Kieninger suggested:
Please make your Support-Sytem more Customer friendly, so that I can send support cases via email and not only use a complicated Ticketsystem (where no ADS is listed) and no phonesystem which wants numbers to be pressed ...

Uniforming SQL syntax (ex. allow float in CAST/CONVERT instead of SQL_Double only) [updated]

2011-12-21T04:46:24-08:00

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.

Ronald Hoek said:

Note, I'm not asking to remove the old SQL_xxx types, only to allow some addition types to be used in the syntax!!!

Uniforming SQL syntax (ex. allow float in CAST/CONVERT instead of SQL_Double only)

2011-12-21T04:27:59-08:00

Ronald Hoek suggested:
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.

Public fields definition requested in data architect

2011-12-20T13:28:50-08:00

Jack Duijf suggested:
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).

Data architect is unable to auto-open IDX index files.

2011-12-20T13:18:16-08:00

Jack Duijf suggested:
If free tables are created using .IDX extension for index files, it is not possible to open the index if the file is open in another connection. A option to auto-open .IDX files (like CDX) would be appreciated.

Make last statement in stored procedure be the result [updated]

2011-12-16T12:23:51-08:00

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

AlexWong said:

nightcrawler,
I think that may be a viable solution. My concern was with statement such as: "SELECT * FROM ( EXECUTE PROCEDURE xxx()) t". In such case, the query engine needs to know the data types of the stored procedure output to process the query.
If my understand your suggestion correctly, then we will have two types of stored procedures. One type (the existing type) has predefined output parameters, and a new type that has no predefined output. The new type of stored procedure, the ones that has undefined output, will not be allowed in place of table input like the sample statement above.

Uniforming SQL syntax (ex. allow float in CASE instead of SQL_Double only) [updated]

2011-12-16T07:49:53-08:00

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.

Ronald Hoek said:

Damn I got a typo in the issue:
I mention CASE, but mean CAST/CONVERT!!!

Allow changing fields of __new table in before triggers [updated]

2011-12-16T00:46:40-08:00

nightcrawler said:

I usually use an instead of insert trigger:
create trigger trig_ins on mytable instead of insert
begin
update __new set id=newidstring(d) where id is null;
update __new set ts=now();
update __new set uname=user();
insert into mytable select * from __new;
end;

Make last statement in stored procedure be the result [updated]

2011-12-16T00:43:01-08:00

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

nightcrawler said:

Alex,
I'd not pre-define the output parameters. Given the case that you want to create some kind of temp table inside the stored procedure to make some fancy stuff like a Pivot table - there's no way to predict the output parameters. They could be that different, dependant on the data, not on a structure.
What about defining the output table if wanted and just give that back if no SELECT (or EXECUTE PROCEDURE) was the last of the statement?
iow if no output cursor was given, do an implicit "SELECT * FROM __output".

Make last statement in stored procedure be the result [updated]

2011-12-15T13:42:31-08:00

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

AlexWong said:

We need some clarification on this.

Are the output parameters still needed to be defined? I think that the answer is yes. And the select list of the last statement must match the output parameter list of the stored procedure.

Uniforming SQL syntax (ex. allow float in CASE instead of SQL_Double only) [updated]

2011-12-15T07:01:00-08:00

Ronald Hoek said:

Note, I'm not asking to remove the old SQL_xxx types, only to allow some addition types to be used in the syntax!!!

Uniforming SQL syntax (ex. allow float in CASE instead of SQL_Double only)

2011-12-15T06:57:56-08:00

Ronald Hoek suggested:
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.

combine Tables, Index, Memo into a single File like we have in other database world, Like SQL server

2011-12-11T00:49:25-08:00

Joseph Owoyemi suggested:
combine Tables, Index, Memo into a single File (Database) like we have in other database world, Like SQL server, MySQL, MS Access etc.

Dangling connections bug? [updated]

2011-11-15T22:20:00-08:00

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?

Ivan Yuzafatau said:

Thanks. I completely missed the method TAdsQuery.AdsCloseSQLStatement().

copy/paste doesn't work well.

2011-11-14T14:21:54-08:00

Mohammad Sanati suggested:
in ARC, please allow to copy/paste using Ctrl+C and Ctrl+V. also Ctrl+Tab doesn't switch between different windows in ARC. unless a grid is focused

Dangling connections bug? [updated]

2011-11-13T21:26:24-08:00

Edgar Sherman said:

Look at AdsCloseSQLStatement and/or NumCachedCursors in the help. They should answer your question.

Live Backup: Implement a file copy if there are no users connected.

2011-11-11T08:10:29-08:00

Ryan Rook suggested:
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).

Dangling connections bug?

2011-11-11T05:11:42-08:00

Ivan Yuzafatau suggested:
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?

Ads.ini [updated]

2011-11-07T15:56:21-08:00

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.

Edgar Sherman said:

The ads.ini file can reside in a number of places such as anywhere in the path or the application directory.

In addition there is an environment variable that can be set (adsini_path) and there are API calls that can be made when an application starts to set this value (i.e. SetEnvironmentVariable).

Does this help?

Ads.ini

2011-11-04T05:30:27-07:00

Ken White suggested:
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.

in ARC32, in the SQL Utility, make it easy to unhide the Data tab

2011-11-02T13:43:54-07:00

Gene Weinbeck suggested:
The data tabbed page for the SQL Utility sometimes disappears on me (I inadvertently click on something or press some magic key combination), and I can find nothing to bring it back.

Allow changing fields of __new table in before triggers [updated]

2011-11-01T17:30:09-07:00

Mohammad Sanati said:

It is very common in database servers to allow modifying the value is begin inserted to updated in before insert or before update trigger