150+ columns SQL table???

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Hi All;

The DataAdapter Wizard does not like more than 99 columns so I have 2
DataAdapters with 2 DataSets. The first fills the first half of the
row and the second fills the second half.

Is this the best way of filling a DataSet with 150+ columns from a SQL
MSDE Database?

Thanks.
 
Honestly the 'best' way to deal with a table like that is not to have one
that big. Assuming that's non negotiable, I think hand coding the adapter
will make updates and everything else a bit easier. The adapters are pretty
much helpless for inserts and updates without the PK field so if that's not
included, they will be of limited use to you either way. Another thing you
may want to consider, and I only say this b/c of the 150 field scenario, is
break it up into smaller queries, each one including the PK. It's doubtful
you are going to use 75 fields on one for (150/2) let alone 150, so if you
can, I'd break it up logically into what's going to be used and include the
PK. Yes, this is still a challenged approach and not advisable in just
about any other scenario, but in this case, I think it's the lesser of
evils.

HTH,

Bill

--
W.G. Ryan MVP Windows - Embedded

http://forums.devbuzz.com
http://www.knowdotnet.com/dataaccess.html
http://www.msmvps.com/williamryan/
 
Um....PK field??

----- William Ryan eMVP wrote: ----

Honestly the 'best' way to deal with a table like that is not to have on
that big. Assuming that's non negotiable, I think hand coding the adapte
will make updates and everything else a bit easier. The adapters are prett
much helpless for inserts and updates without the PK field so if that's no
included, they will be of limited use to you either way. Another thing yo
may want to consider, and I only say this b/c of the 150 field scenario, i
break it up into smaller queries, each one including the PK. It's doubtfu
you are going to use 75 fields on one for (150/2) let alone 150, so if yo
can, I'd break it up logically into what's going to be used and include th
PK. Yes, this is still a challenged approach and not advisable in jus
about any other scenario, but in this case, I think it's the lesser o
evils

HTH

Bil

--
W.G. Ryan MVP Windows - Embedde

http://forums.devbuzz.co
http://www.knowdotnet.com/dataaccess.htm
http://www.msmvps.com/williamryan
 
Layered tabs is generally a bad idea, altho with limited real estate on a
PPc, it is extremely tempting for CF. But do check out the "Interface Hall
of Shame"
http://digilander.libero.it/chiediloapippo/Engineering/iarchitect/index-1.htm

I would also strongly urge you to normalize the data at least to first
normal and either use separate adapters or joins to bring in what you need.
Especially in a CF app, trying to pull in that many columns at once must be
enormously expensive in terms of CPU usage.

Mike said:
lol - no - for user ease of use I am using a TabControl to display/collect
Click to expand...
code type data. 12 tabs with 13 columns per. I could split each tab as a
separate row....I may have to do that anyways....due to the limits.
 
Back
Top