Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!tank!dwayne@rover.bsd.uchicago.edu
From: dwayne@rover.bsd.uchicago.edu
Newsgroups: comp.databases
Subject: Ingres is making me mad!!
Message-ID: <1949@tank.uchicago.edu>
Date: 21 Feb 89 22:13:37 GMT
Sender: news@tank.uchicago.edu
Organization: University of Chicago - Biomedical Physics
Lines: 22

I am working on a medical study which essentially makes no sense to
break up into smaller tables.  It is basically a questionairre 80% of
which are y/n/u questions.  Intermixed, of course, is floating point
and character data types.

Well, I hit that legendary boundary of 127 columns in a table early
on, so we whittled the data set down to that size.  Now I set up an
ABF call to QBF which calls up my ViFRED form no problem.  But if I
try to either retrieve or modify then QBF tells me that there are too
many fields, it then returns to the QBF main menu.

Like I said before, breaking my questionnaire up into several tables isn't
what I want to do.  Selects will get hairy, and frankly I would prefer that
our physicians just use the default query mechanisms of Ingres.  So, with
that in mind, does anybody have any ideas that might help me get around
this (I think undocumented) limitation???

Thanks in advance...

Dwayne

P.S. I'm running Ingres vers.5 under VMS vers.4.7.