Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!husc6!hscfvax!pavlov
From: pavlov@hscfvax.harvard.edu (G.Pavlov)
Newsgroups: comp.databases
Subject: Re: Ingres is making me mad!!
Message-ID: <730@hscfvax.harvard.edu>
Date: 22 Feb 89 05:00:47 GMT
References: <1949@tank.uchicago.edu>
Organization: Health Sciences Computing Facility, Harvard University
Lines: 22

In article <1949@tank.uchicago.edu>, dwayne@rover.bsd.uchicago.edu writes:
> I am working on a medical study which essentially makes no sense to
> break up into smaller tables....
> 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.
> 
> ......  So, with
> that in mind, does anybody have any ideas that might help me get around
> this (I think undocumented) limitation???
> 
  This limitation drives us nuts (we work with medical data also).  With all
  the real improvements, many quite complex, that RTI has been/is implementing,
  it does not seem that changing this would require quite that much effort.

  You're stuck.  Simplistically speaking, almost anything you do will result
  in the "creation" of a table (logical, real, or otherwise...), and the 
  limit applies to any manifestation of such.

  greg pavlov, fstrf, amherst, ny