SQL Server Triggers: Last Inserted Identity is for Child Record not Parent (Alpha Five V10 and older)
/documentation/pages/Guides/Databases/Troubleshooting/AlphaDAO SQL Server Identity Fields Triggers Bug.xml

In Alpha Five Version 10 and prior, an issue exists where the identity returned for the last inserted record is for a child table and not the master table. This issue only applies to SQL Server where an Insert Trigger has been defined. This issue is fixed in Alpha Anywhere.

Variable Scoping and Nested WITH ... END WITH Commands
/documentation/pages/Guides/Xbasic/Other Xbasic Topics/Variable Scoping and Nested WITH __ELLIPSES__ END WITH Commands.xml
When you nest WITH ... END WITH commands, it is important to understand how Xbasic treats variables DIMmed in different name-spaces. If a WITH ... END WITH command is nested within another WITH ... END WITH construct, the inner name-space is called the child name-space and the outer name-space is the parent name-space. Any variable that is DIMmed in the parent name-space will be visible in the child name-space. Any variable that is DIMmed in the child name-space will not be visible in the parent name-space (unless the variable name is prefixed with the name-space name, as in: name-space.variable ). The following Xbasic script demonstrates this. In this script, "A" is the parent name-space and "B" is the child name-space. The variable, firstname is DIMmed in the parent name-space. It is therefore visible in the child name-space.
Getting the Value of an Auto-Increment Field
/documentation/pages/Server/Reference/Design/Data/SQL/Getting the Value of an Auto-Increment Field.xml
Say you inserted a new record into the customer table, and did not assign a value to the customer_id field, because this field is an auto-increment field. In many applications, after a record is inserted, it will be important to know what value the database engine assigned to the auto-increment field (note that a table can only have a single auto-increment field). The technique used to find the value of the auto-increment field varies depending on the type of back-end database that you are using. In the following example, we use a technique that works with SQL Server, Access, and MySQL. It may also work with some other databases, but certainly will not work will all databases. You will need to refer to the documentation for your database to see what method they use.
Alpha Five V11
/documentation/pages/Index/Alpha Five V11.xml
Page links and information relating to A5 V11.
How to Use User-Defined Scalar Functions in Oracle and SQL Server
/documentation/pages/HowTo/Databases/Call User Defined Scalar Functions in SQL Server Oracle.xml
User-defined scalar functions in Oracle and SQL Server can be called from Alpha Anywhere.
SQL::Connection GenerateLastInsertedIdentityStatement Method
/documentation/pages/Ref/Api/Namespace/SQL/Connection/GenerateLastInsertedIdentityStatement Method.xml
Generate a SQL statement to retrieve the identity from the last insert statement (may be specific to the table passed in).
What's New in Version 11
/documentation/pages/Index/What's New in Version 11.xml
Welcome to Alpha Five Version 11! If you thought we added a ton of functionality in Versions 10 and 10.5 plus the Feature Packs, you may have to recalibrate your notion of what defines a "ton of functionality".
SQL::Connection LastInsertedIdentity Method
/documentation/pages/Ref/Api/Namespace/SQL/Connection/LastInsertedIdentity Method.xml
Returns the last inserted identity for a specific table (where possible) after executing an INSERT statement.
How to Setup Production and Development Versions of Your Web Application with the Alpha Anywhere Application Server for IIS
/documentation/pages/HowTo/IIS/Publishing Test and Production Sites.xml

Learn how to publish separate production and test sites for your web application.

AlphaDAO - Stored Procedures and Output Arguments on the SQL Server
/documentation/pages/Guides/Databases/Stored Procedures/AlphaDAO - Stored Procedures and Output Arguments on the SQL Server.xml
If you have a SQL server stored procedure that sets the value of an output argument, reading the value in the output argument, after the stored procedure has executed can be tricky. That's because you have to ensure that you first loop through all of the result sets that are returned by the stored procedure before reading the output arguments.