I've been mentally trying to construct a fairly long addition to
this thread in spare moments for a couple days now...  And
just not getting there....  So I'll try something unusual:  I'll omit
the leader and cut right to the chase (making Stan and many
other happy, no doubt...    ;-)   ):


If HP does not / cannot commit to bundling the full ALLBASE
product with Image/SQL (missing ninth out of nine modules)
*and* bringing ALLBASE fairly quickly up to full compliance
with the SQL99 standard (would be nice, but I'm not exactly
holding my breath), then how about:

Modifying the IMAGESQL utility to allow an option to ATTACH
a TurboIMAGE database over the network to a MS SQL/Server
7.0 and up DBE on NT / Win2K ??....

Freely admit I have no idea of the difficulty, but conceptually
seems like it should be possible.  Even if there were (and expect there
would be) some limitations, seems like being able
to use SQL/Server as a direct front-end to TurboIMAGE
instead of Allbase could solve a lot of technical and political
problems.

Yes:  I know that from one perspective this is heresy;  in that
it makes an NT server connected to your e3000 part of the
core requirement for doing any kind of SQL / ODBC access
to TurboIMAGE....  I've pretty much come to the conclusion
that in the current real world that is the lesser of two evils....
.... and in fact that it might be the best of both worlds....

Comments ??

Ken Sletten