remote operation via DSL connection??

[Markus Frey]

Hello dear ACCESS-users,

my problem is, that I want to operate an MS ACESS database with connected
tables
to a second MS ACESS database via a DSL (flat-rate) connection, but the data
transfer
via DSL between these two databases makes the operation very slow.
Maybe someone can give me an idea, how the data transfer to connected tables
in MS ACCESS
works, an how I can apply some optimations in order to make the operation
faster.

Maybe, there are some other ideas or possibilities to proceed a remote
access between to
MS ACCESS databases????

Thanks very much for every contribution or idea!

Mark

[Pavel Romashkin]

Avoid using bound forms, or at least bind them to queries that select
TOP xxx instantly visible rows from the remote database tables instead
of selecting all records.
Using a terminal server is another option I heard good things about.

Pavel

Markus Frey wrote:

Hello dear ACCESS-users,

my problem is, that I want to operate an MS ACESS database with connected
tables
to a second MS ACESS database via a DSL (flat-rate) connection, but the data
transfer
via DSL between these two databases makes the operation very slow.
Maybe someone can give me an idea, how the data transfer to connected tables
in MS ACCESS
works, an how I can apply some optimations in order to make the operation
faster.

Maybe, there are some other ideas or possibilities to proceed a remote
access between to
MS ACCESS databases????

Thanks very much for every contribution or idea!

Mark

[David W. Fenton]

ma********@surfeu.de (Markus Frey) wrote in
<bt***********@ulysses.news.tiscali.de>:

Maybe, there are some other ideas or possibilities to proceed a
remote access between to
MS ACCESS databases????

The bandwidth available to DSL is simply not enough for an Access
to Jet application, no matter how carefully written. DSL is, at
best, 1/10th the bandwidth of 10BaseT (i.e., 1/10th the speed of a
modern LAN).

If there's a Windows 2000 server on the either end of the
connection, you should consider Windows Terminal Server. Win2K
comes with a license for up to 2 simultaneous connections, and it
works extremely well. I support a number of clients in this
fashion, and do most of my programming for one of them in terminal
server (the choice would be to travel to their office and they no
longer want to pay a premium to me for that).

Your other option is to use a remote control program such as PC
AnyWhere or, in my opinion a better alternative, VNC. However, this
is not the best environment, as it is simply not as fast or as
user-friendly as WTS. It's fast enough over DSL for occasional
work, but not for daily work.

The last option would be converting the data store to SQL Server,
but that involves a lot of issues, including security and
performance, that the other two do not. That is, it could require
substantial re-architecting of your application.

From my point of view, Windows Terminal Server is by far the best
available technology for supporting remote users nowadays. Indeed,
it's enough to justify converting to Win2K Server where it's not
already in use.

--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc

[Albert D. Kallal]

I can't add anything to David's comments in this thread.

Terminal services is great way to go, and it gets my vote also.

You can read my thoughts on using a wan with ms-access.

Using a wan with ms-access? How fast, how far?
By Albert D. Kallal
Saturday, August 09, 2003

Using a wan with ms-access. - a instant network primer.

http://www.attcanada.net/~kallal.msn/Wan/Wans.html
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
No************@msn.com
http://www.attcanada.net/~kallal.msn