General on UserVoice

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

Allow changing fields of __new table in before triggers

2011-11-01T17:29:19-07:00

Restore to empty folder

2011-10-31T11:06:46-07:00

Charles Wolfe suggested:
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).

Advantage does not support "Select Into" a link db [updated]

2011-10-21T05:45:45-07:00

eg. Select * into LinkDB.Table1 from Table1 causes a SQL error. This is a very useful feature that allows one to quickly make a copy of an entire table (or selected record) from say a live database to a test/dev database.

Stefan Hirsch said:

Also StoredProcedures (like sp_ZapTable) are causing this error. Links should be supported in AdsOpenTable().

Consolidated Database

2011-10-19T17:02:50-07:00

Mohammad Sanati suggested:
Combine all .dbf and .adt files into one solid database file. this will make the database more consistent and secure. This might be optional for the users who prefer to have one or very few data files instead of hundreds of legacy files.

Make ADSDOSIP work with Windows 7 [updated]

2011-10-14T09:24:44-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.

mhagman said:

The latest version can be downloaded with the Clipper client from the DevZone at
http://devzone.advantagedatabase.com/dz/content.aspx?key=20&Release=16&Product=19&Platform=6

Make ADSDOSIP work with Windows 7 [updated]

2011-10-13T09:17:50-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.

HOS said:

Hi Jeremy
I realise quite some time has passed since the point was discussed.
I'm trying to get a copy of the latest ADSDOSIP. Where can I get it and what is the latest version?

top

2011-10-05T07:48:49-07:00

Ron WYman suggested:
Allow declaired varables to be used in the TOP function. E.G. declare @x integer; @x=1; Select TOP @x from ....

Query slow [updated]

2011-09-20T13:51:48-07:00

Dear Sirs, I use ADS version 10.00.0.3 and Delphi 2010. A few days ago, a client told me slow issues when querying some tables from the database. There are actually three tables that are most frequently consulted. The tables have the following sizes: Table 1 = 19 MB - 25,962 records Table 2 = 11 MB - 3259 records Table 3 = 158 MB - 53,999 records Imagine the following situation: In a network with 4 machine and a dedicated database server where the database is in dedicated server and application that is installed on client machines and 4 each has the file ADS.INI pointing to the server. If the application is started on machine 1 and the application is made within a query in Table 1, the response time is milliseconds. If the application is open on machine 2, the same query in the same Table 1, the response time leaves a few milliseconds to 10 seconds. If the application is open on machine 3, the query is made in Table 1, the response time is approximately 13 seconds. If all four machines are connected to the database while making operations, the response time of each machine is about 15 seconds for each query, reaching up to 20 seconds. The times listed above is for each of the machines making simultaneous queries in Table 1 that has 19 MB with 25,962 records. In a particular application module, tables 1, 2 and 3 are used together with queries and data entry. Thus, the whole process is extremely slow. In the application, the SQL queries in the tables are quite simple. For example, in Table 1 using the component TAdsQuery do the query as follows: Begin With The MD.QyCadProdutos Close; Sql.Clear; Sql.Add ('SELECT *'); Sql.Add ('FROM CadProdutos'); Sql.Add ('WHERE'); Sql.Add ('(CodGrupo) =: Par0'); Params [0]. AsString: = Edit1.Text; Open; end; The response time for the code above is only milliseconds to a machine connected to the database and goes up to 20 seconds as other machines are connecting to and querying the same table. My procedures were 1 °) reindex tables; 2) create a new table and enter the registry and recreate the indexes; 3) increase the contents page of 512 to 1024 until you reach the limit of page elements, and 4) Replace the DLL from the database in each of the machines that connect to the database. None of these operations got success! The network is fully certified and with little traffic. There is no wiring board with problems or damaged. This problem started almost from night to day, or there was something that was slowing down. Just slow and appeared settled. Does anyone have any idea or solution to the problem? Thanks, Rogério.

Edgar Sherman said:

I would suggest opening up a Support case or using the newsgroups or StackOverflow to ask support questions.
However, I will offer a suggestion. Ensure that the application is connecting to the ADS REMOTE SERER and is not silently scaling back to LOCAL SERVER. The behavior you are describing leads me to believe your applications have fallen back to LOCAL SERVER.

Database Mirroring [updated]

2011-09-15T14:24:12-07:00

Synchronous high-safety mode and asynchronous high-performance mode to increases data protection and provides complete or almost complete redundancy of the data.

Goran Sedlar said:

Database Mirroring is important to me because business of my clients growing and they need more security and better disaster recovery strategy.

Database Mirroring

2011-09-15T14:10:19-07:00

Goran Sedlar suggested:
Synchronous high-safety mode and asynchronous high-performance mode to increases data protection and provides complete or almost complete redundancy of the data.

XE2 Support [is now started]

2011-09-15T13:21:34-07:00

Support Embarcadero Delphi XE2

AdsDDFreeTable

2011-08-22T00:37:11-07:00

ThomasF suggested:
when use AdsDDFreeTable with a free Table retourncode should not be 5199

arc keyboard shortcut shortcoming

2011-08-10T17:30:14-07:00

Luis Krause suggested:
When using the keyboard to execute certain options, the focus never returns to the grid. Example: I hit ctrl+delete to mark a DBF record for deletion, then Alt+A, K to pack the table. I can't then use the navigation keys to move through the grid because the focus is stuck go figure where... so I have to reach for the mouse, defeating its usefulness.

Collate doesn't work if a query contains parameters [updated]

2011-08-10T08:44:56-07:00

This works... select * from system.columns where name = 'test' collate ads_default_ci This does not... select * from system.columns where name = :param collate ads_default_ci param = 'test'

Andrew said:

This is the error that follows...
poQuery: Error 7200: AQE Error: State = 42000; NativeError = 2117; [iAnywhere Solutions][Advantage SQL Engine]Unrecognized token collate -- Expecting semicolon. -- Location of error in the SQL statement is: 50

Collate doesn't work if a query contains parameters

2011-08-10T08:42:19-07:00

Andrew suggested:
This works... select * from system.columns where name = 'test' collate ads_default_ci This does not... select * from system.columns where name = :param collate ads_default_ci param = 'test'

Collation mismatch bug? [updated]

2011-08-08T13:55:37-07:00

Creating a secondary index on an ADT table cicharater field with CharType GENERAL_VFP_CI_AS_1252 causes an BrowseTable Error 5209: Different collations are being used, which can result in poor query optimization. Table collation: (none), Index collation: GENERAL_VFP_CI_AS_1252 This issue occurs in any cases, even if the table was build in ARC with CharType GENERAL_VFP_CI_AS_1252 specified in the Connection Properties. Probably secondary indexes can only be built with CharType ANSI, while FULLTEXT indexes can be built with CharType GENERAL_VFP_CI_AS_1252. If secondary indexes can't be build with GENERAL_VFP_CI_AS_1252, they should automatically be built with CharType ANSI without index collation mismatch messages, shouldn't they? I think something goes wrong here. If this is a bug, please fix it ASAP for Advantage 9.1.

josheryn said:

I believe this page from the help file explains what you are seeing - http://devzone.advantagedatabase.com/dz/WebHelp/Advantage10.1/index.html?arc_dynamic_collation_mismatch_5209_error.htm

Data Architect filter issue [updated]

2011-08-08T07:40:30-07:00

Gents ... first off Thank You, for the filter options on verion 10.0 of the Data Architect. However it isn't working as it should. If I filter but "OS Login" and "Connection Name" I it doesn't appear to be filtering on "OS Login" at all.

mhagman said:

Hi Greg -

Thank you for the input. In order to get a quicker response in the future please post these type of question to the Support Newsgroups http://devzone.advantagedatabase.com/dz/content.aspx?key=7

email Advantage@ianywhere.com.

Collation mismatch bug?

2011-08-03T13:09:47-07:00

tmc3 suggested:
Creating a secondary index on an ADT table cicharater field with CharType GENERAL_VFP_CI_AS_1252 causes an BrowseTable Error 5209: Different collations are being used, which can result in poor query optimization. Table collation: (none), Index collation: GENERAL_VFP_CI_AS_1252 This issue occurs in any cases, even if the table was build in ARC with CharType GENERAL_VFP_CI_AS_1252 specified in the Connection Properties. Probably secondary indexes can only be built with CharType ANSI, while FULLTEXT indexes can be built with CharType GENERAL_VFP_CI_AS_1252. If secondary indexes can't be build with GENERAL_VFP_CI_AS_1252, they should automatically be built with CharType ANSI without index collation mismatch messages, shouldn't they? I think something goes wrong here. If this is a bug, please fix it ASAP for Advantage 9.1.

Data Architect filter issue [updated]

2011-08-02T09:56:17-07:00

josheryn said:

Can you post the filter that you're trying to use? Are "OS Login" and "Connection Name" fields in your table?

Data Architect filter issue [updated]

2011-08-01T04:02:38-07:00

Greg Rickson said:

Some-one HELP please ???

Provide way to keep connection alive when user's computer is inactive for awhile

2011-07-27T10:16:05-07:00

billseven suggested:
There is a Windows feature with a default setting that powers down network cards automatically after awhile. We need a way to have the connection with the ADS server stay alive during periods of inactivity by users, would be nice if the component had a keepalive property that would handle this