Denys Beauchemin <[log in to unmask]> wrote:
 
<snip>
 
>OK, question 1.  How many of you out there are actively using IMAGE/SQL
WITH
>SQL access?  Not just to say "We have updated to IMAGE/SQL," but rather,
"we
>have attached production databases and we are accessing the data in IMAGE
>through the SQL interface".  It doesn t have to be totally SQL, but a least
>some portion of it, perhaps ad-hoc reporting, should be in SQL.
 
You got another victim here -- we're accessing 10 - 15 production databases
via the SQL interface.
 
>Question 2.  How many of you are actively accessing attached IMAGE/SQL data
>via ODBC or other middleware in a client/server fashion to PCs?  How are
you
>doing it?  Which end-user tools (shrink-wrapped or otherwise) are you
using?
> Are you developing with VB or perhaps something else?
 
Were using: HP's InformationAcess with both the native interface and ODBC,
Microsoft applications (Query, Excel, & Word) via ODBC, and some Ingres
applications running on HP/Apollo workstations using the Ingres/Allbase
gateway, Ingres/Net and Allbase/Net.  We've got three projects going using
Axiant as the client, but these are slated to use Ingres on the server --
however we may do a trial deployment using Allbase first.
 
>Question 3. If you are not now currently using IMAGE/SQL with SQL, why not?
 
 
>Question 4. If you are using attached IMAGE/SQL databases with SQL but are
>not doing client/server access, why not?
 
Regards.
 
 -- Evan