R
Rich
I'm sure it sounds kinda nutty to display 200 columns and
500,000 rows of data. But I have been pulling data from a
Lotus Notes database into Sql Server for a while now, but
Lotus Notes is starting to crack, columns getting
corrupted. Can't handle the volume of data and number of
columns. Sql Server has no problem. But displaying the
data is the big deal. The end users want to be able to
scroll acros a page to the colum of their choice, or be
able to scroll up or down. I was thinking of breaking up
the table into section, but this would reqire additional
clicking to get to the next section of the table. Would
it be feasable to have a 200 column table in asp? or
should I stick with the section idea? I have to tell my
dept something. They started out with Lotus Notes but
couldn't query the data. I have been suggesting to
migrate the project entirely to Sql Server/IIS. Notes can
at least display all the columns. Suggestions appreciated.
Thanks,
Rich
500,000 rows of data. But I have been pulling data from a
Lotus Notes database into Sql Server for a while now, but
Lotus Notes is starting to crack, columns getting
corrupted. Can't handle the volume of data and number of
columns. Sql Server has no problem. But displaying the
data is the big deal. The end users want to be able to
scroll acros a page to the colum of their choice, or be
able to scroll up or down. I was thinking of breaking up
the table into section, but this would reqire additional
clicking to get to the next section of the table. Would
it be feasable to have a 200 column table in asp? or
should I stick with the section idea? I have to tell my
dept something. They started out with Lotus Notes but
couldn't query the data. I have been suggesting to
migrate the project entirely to Sql Server/IIS. Notes can
at least display all the columns. Suggestions appreciated.
Thanks,
Rich