Hi.

At last i've connected across internet a client but i think it's too slow for my customers.

Any way to improve this connection?

Thank you.

Francisco,

you can try to set Session.RemoteCompression to 9.

If it is still too slow (and I think it will be, unless you optimize your application to
cause minimum network traffic) you can take a look at the replication feature of EDB.

http://www.elevatesoft.com/manual?action=mantopic&id=edb2sql&category=0&topic=21

Heiko

Heiko,

Yes, it a little faster but not enougth. About replication i think that a terminal server
session is by now easyest and faster for my requirements

Thank you very mutch

Francisco,

<< At last i've connected across internet a client but i think it's too slow
for my customers. >>

Is your application designed for low-bandwidth situations ?  If not, then
you will most likely not be happy with the performance over the Internet.
You can't use things like lookup fields and other TDataSet architecture
features that cause the application to become too "chatty".  The latency on
the Internet is much greater than a LAN, and can cause the turnaround time
on a single request/response pair to be much greater than you would expect,
so reducing the number of requests/responses is the most important aspect of
such an application.  You also have to use features like the RemoteReadSize
property in EDB to reduce the number of requests for rows when navigating
datasets:

http://www.elevatesoft.com/manual?action=mancompprop&id=edb2&product=d&version=7&comp=TEDBDataSet&prop=RemoteReadSize

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

As you say my application is not designed for low-bandwith. It's designed too interactive
and will be complicate change it because i would must change all application and all
components. In this moment my customers are happy with this interactive components and if
i change it they can kill me. Then, for a few remote connections i will need i prefer
install a terminal server session.

Thank you

Francisco,

<< As you say my application is not designed for low-bandwith. It's designed
too interactive and will be complicate change it because i would must change
all application and all components. In this moment my customers are happy
with this interactive components and if i change it they can kill me. Then,
for a few remote connections i will need i prefer install a terminal server
session. >>

That's fine.  Just to clarify - designing for low-bandwidth situations
doesn't mean giving up any functionality in the application.  It simply
means doing certain things differently in order to avoid too many
requests/responses to and from the ElevateDB Server, such as caching lookup
tables locally.  It can also mean better load balancing also by allowing
long, data-intensive processes to run on the ElevateDB Server as stored
procedures, scripts, or jobs and have the client-side deal with more
UI-specific issues.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

What is lookup fields?

Francisco,

<< What is lookup fields? >>

Search on "lookup columns" in the Delphi help for more information.

--
Tim Young
Elevate Software
www.elevatesoft.com