🚀 go-pugleaf

I'm pretty unsure that you need all columns simultaneously. So you may bind
your TADOTable to some View (or SELECT for Access).
In any case it's probably a bad database design...;)))

HTH,
   Alexei.

"Lance Robaldo" <lance@e-machines.net> wrote in message
news:3a8405fd_1@dnews...
> We're using an Oracle 8i database and we have a table with 478 columns, I
> know, that's a LOT of columns, but we need them this way, it would be VERY
> impractical to break them up into multiple tables.
>
> If I use a TTable, I have no problems at all, other than it's S L O W.
>
> But if I use a TADOTable with Client-side Cursor I get a "Too many
columns"
> error.  If I change it to a Server-side Cursor I can open and read the
> dataset, but I can't use controls that display multiple rows (like
dbGrid).
>
> Is there any work around to this?  I'd like to use ADO because it's
> substantially faster, but I can't use it if it doesn't allow me to have a
> lot of columns, or if it won't work with multi-record components.
>
> Thanks.
>
> Lance Robaldo
> lance@Robaldo.com
>
>