Hi all,
 
Well, with the application of much harsh language we finally got JetForm
working with Allbase/SQL (although I should note that it works in a very
strange way: it seems to use both the ODBC and HP/Gupta APIs simultaneously
 -- JetForm is looking into that).
 
One of our developers just started another project with JetForm and he's
seeing some very strange things:  There's JetForm dialog box for mapping
field names on the form to column names in the database; in the column names
fields in this dialog box he's seeing a lot of garbage characters in the
field names.  Interestingly, when he uses a clone of the table that's
implemented in dBase he doesn't experience the problem.
 
The difference, BTW, is that JetForm has a native driver for dBase, but is
using ODBC (and maybe a little bit of HP/Gupta) to access Allbase.
 
Another interesting point is that each row contains about 650 bytes of data.
 When he reduces the amount of data by defining only a couple of fields,
then he doesn't experience the problem.
 
Has anyone out there seen anything like this?  I'm starting to wonder if
perhaps ODBC has some limit as to the length of the row -- or the number of
columns in a row, that can be retrieved...
 
And while I'm at it...I mentioned that JetForm seems to use both ODBC and
HP/Gupta simultaneously: has anyone seen anything like that, either with
JetForm or with Q+E (which JetForm uses)?  (We thought the developer had
merely done a sloppy job of setting up the connectivity to Allbase; we spent
an afternoon cleaning it up so that only ODBC would be invoked.  When we
then ran JetForm it caused a real pretty GPF in ODBC.DLL.)
 
TIA
 
 -- Evan