Unify Q 1.0.1 Now Available!

Unify Q 1.0.1 is now available. This new release of Q introduces many enhancements that have been requested by early users. These enhancements to Q provide a smoother experience and intuitive touch.

• Managing connections: improved enhancements eliminate the need to manually edit configuration files.
• Flexible queries: new parentheses are now available for query condition support.
• Improved usability when defining queries: duplicate column names are now preceded with the table name to avoid selecting undesired columns.
• Easy upgrading: update your existing Q installation by running the installer downloaded from our website. No new PMC or product activation/registration is required.

Download Q 1.0.1

Buy Unify Q 1.0.1

Several conditions can now be grouped together by placing brackets around the desired conditions.

Duplicate column names are now preceded with the table name when defining queries.

More News

SQLBase EDP Benefits

Create a seamless user experience for your customers using SQLBase EDP. Let your customers enjoy a single and easy setup of your application. With SQLBase EDP, there is no need for your customers to enter PMC codes or activate and register the software. Just install and go.

For ISVs, the SQLBase EDP provides a number of benefits. The per seat pricing that allows selling any number of seat configurations to customers is very flexible and cost effective. The SQLBase EDP saves money when compared to the multi-user pricing for fixed amount of user SQLBase servers.

SQLBase EDP Benefit Summary

• Saves on SQLBase licenses. Create any number of SQLBase users for your customers instead of using a predefined amount of a user’s server that might provide more users than necessary. The SQLBase EDP lets you create for example 3-User servers, 11-User servers, or any amount of users your customer needs.
• Creates a seamless installation experience for your application and database.
• SQLBase EDP lets you create preconfigured SQLBase installations that have a daily automatic backup configured through the new SQLBase Command Center.

Team Developer 6.0 Update

The Team Developer 6.0 development team is making huge progress on the new .NET compiler and other features in the upcoming Team Developer 6.0. The team has added more features than initially unveiled at last year’s Developer Conferences. For example, external function calls (Win32) for .NET build targets were originally unsupported. The development team has now built in support for external function calls when .NET build targets are selected, with one exception, and that is when structures are being passed or received from external functions. This latest addition to the Team Developer 6.0 feature set will make your move to TD.NET applications faster and easier.

With Team Developer 6.0, you will be able to call .NET Class Libraries (DLLs) from within applications compiled for Win32 and .NET.

Overview of Team Developer 6.0

We will continue to keep you posted on the latest developments in Team Developer 6.0.

LATAM DevCon Summary

The Latin America Developer Conferences (DevCons) hosted in Mexico, Peru, Argentina and Brazil, April 6-15, brought more than 160 attendees from all over Latin America together to view SQLBase, NXJ, and Q, and preview the upcoming Team Developer 6.0 (.NET) release.

DevCon attendees, including some of our existing customers, were very interested in the TD .NET version and excited about the new ability to have several options to compile using the same GUI. Some customers are even putting projects on hold for the release of the .NET version.

A special thanks to the four partners that made this year’s Latin America DevCons a success:

• ACSISA - Mexico
• BSI - Peru
• SAM Sistemas - Argentina
• Triad Systems - Brazil

View pictures from Latin America DevCons

Tips & Tricks

Passing LONG VARCHAR data type columns into a stored procedure from a trigger

Contributor: Mike Vandine, Senior Technical Support Consultant

According to the SQL Language Guide, passing LONG VARCHAR data type is not possible. In the sub-chapter ‘Create Trigger’, it states:

"Columns of LONG VARCHAR data type are not supported. This means that you cannot pass a LONG VARCHAR column as a parameter to a procedure."

So what do you do if you MUST pass a LONG VARCHAR column? You can't actually pass the column itself, but in the trigger you can pass the rowid to the procedure and the procedure then can read the just-updated row and retrieve the LONG VARCHAR directly into a local variable. Once you've got the column value in the procedure, you can do anything that you like with it. Here is a simple example:

create table table1 (id char(4), text long varchar);
create table table2 (id char(4), text long varchar);

store strtest
Procedure: strtest static
parameters
string: strRowid
local variables
string: strId
long string: strText
actions
call sqlimmediate('select id, text into :strId, :strText from table1 where rowid = :strRowid')
call sqlimmediate('insert into table2 (id, text) values (:strId, :strText)')
return 0;

CREATE TRIGGER audittest after update on table1
(EXECUTE strtest (rowid))
for each row;

insert into table1 (id, text) values ('1234',:1)
\
$DATATYPES CHARACTER
"ABCD",
/
select * from table1;
update table1 set id = '2345';
select * from table2;

Table2 will now have the Id of 2345 and the long varchar column value of ABCD.

Please note that this must be done in an 'after' trigger so the rowid is the value after the update or insert.