Hi All,

I am asking this because I would not know where to start with
a way to test the load on the server and local machine:

I have to keep up with a certain amount of data. It is based on
numerous fields for a given day of a given month. One way is to
have one record that has 31 fields each of 10 different types (it wins up being a 5k record) of information (Numeric) such as a
start, end, duration, difference, etc numeric fields for each day.
The other way is to have a single record for each day, giving 31
records each of about 10 numeric fields. Each record is less than
150 bytes. I can then filter based on a week tally, bi-month tally, etc.

The kicker is that the information needs to be seen in a left to
right, by day, top to bottom by field view on screen.

As you can imagine the view is slow either way. I am trying to see
if having 31 different TIB_Querys is better than having a single
huge query record. I can break up the visible screen information to
one half month per view at a time but it is still slow painting the
data on screen.

The issue I see is whether each of the TIB_querys would have an impact on the database server or just on the client pc. One buffer
connection per table or just one connection for the IB_Connection?
I tried including a couple of querys at a time and running the
program over and over but could not get a real handle on what the
eventual load on the server would be.

Any help would be appreciated.

Thanks