We still use AQ  as well.
(AQ/3000 is the old Advanced Query 3000 still found in the
contributed library)
We are trying to wean ourselves to Query for ad hoc online queries
but AQ has a number of nice features Query still doesn't have, and
it's a great report writer. One problem, we just starting using reals
in our databases and AQ doesn't handle them.

And, as far as we're concerned, AQ3000 IS Y2K COMPLIANT.

What makes you think it isn't?

AQ's internal date format(D1 item, same space as an I1) is good 'till
Dec 31, 2029(1=01/01/1930). (Adager knows of this item type and
does conversions on it).  This, of course, is only a concern if you
use the internal AQ date format.  We've moved away from D1 items and
use character fields for dates.

3k does have the source code for AQ3000, but I don't think their too
involved in it. We got the source code  fom Chris Bartram and our SPL
guy looked through it with the idea of adding real number support,
but we didn't get too far. He characterized the source code as
Byzantine.

Bob.

On 25 Oct 99 at 11:29, Nathan Hunt wrote:

> Nathan,
>
> Can you answer a question?
>
> 1.  What is AQ/3000 and what does it do?  (In other words, is it an
> integral, critical part of your environment?)
>
>         AQ/3000 is an overgrown version of Query/3000.  Instead of Query, we
> use AQ.  We currently have numerous, over 100, AQ/3000 procedures (query
> procedures) that are used daily/weekly intensively.  The conversion time
> would be tremendous.
--=--=--
Bob Walker, Computer Centre  --  [log in to unmask]
Capilano College, North Vancouver, BC, CANADA.
------
'No one is listening until you make a mistake.'