How to improve performance over slow connection

Hi,

I am using V2.08.03.

I must display a table with a few records and 40 columns to my users.
The result will be display in a read-only grid. The user will be able to regroup and
reorder the grid (cxGrid) to see grouping total, footer summaries, colorsetc...
It's taking some time to complete some operations. Are there any tips to help improve
the performance.

Oh! BTW. Did I mention that the Database server is on a building and the customer on
another? They are linked through Wifi.

The form has a few search fields and a filter button. Once the user presses the
filter button, I open the query to fetch all the requested records.
Do you know if cxGrid refetches the rows for each regrouping? (it seems to me it is,
but hasn't done any testing)

TIA,
Clément

ClémentDoss wrote:

> The form has a few search fields and a filter button. Once the user presses
> the filter button, I open the query to fetch all the requested records.

I would recommend to use TnxCachedDataSet to pull the full resultset over the
network in a single message and put it into a local in-memory table.

That way it doesn't matter if the grid keeps coming back to the dataset all the
time or not.

ClémentDoss wrote:

> Hi Thorsten
> >
> > I would recommend to use TnxCachedDataSet to pull the full resultset over
> > the network in a single message and put it into a local in-memory table.
>
> What would be the correct way to do it then?
> Put a local server in the client application. Link the CachedDataset to the
> remote server, Open it, then copy the records to a memory dataset linked to
> the local server?

The TnxCachedDataSet (via it's Database property) needs to be a linked to a
"local" TnxServerEngine (you can use a AliasName of #inmem on the TnxDatabase).

You then connect the SourceDataSet to the TnxQuery that's connected to the
remote server.

There is no need to open the TnxQuery, just set up the query text and params.
When you then open the TnxCachedDataSet, it will execute the query, pull over
the resultset using BatchRead(s) and close the query again.

Hi Thorsten
>
> I would recommend to use TnxCachedDataSet to pull the full resultset over the
> network in a single message and put it into a local in-memory table.

What would be the correct way to do it then?
Put a local server in the client application. Link the CachedDataset to the remote
server, Open it, then copy the records to a memory dataset linked to the local server?

TIA,
Clément