Access speed to FMP5 db over dial up

[RAP]

I'm interested in serving a FMP5 database over TCP/IP and am experiencing very slow response rates. I'm seeking ways to achieve acceptable speeds.

Server: Mac G3, FMP5 dbase file, served over 128 kbps ISDN line, static address, via AppleShareIP

Remote Users: with FMP5 stand alone application opening the served dbase over dial up modem connection (effective speeds of 28.8 - 31.6 kbps); connecting to the database via AppleShare as if it were a local Mac

My tests give me 36.5 seconds to open the dbase, 52 sec to open the form layout and 6 sec to view as List. Over the LAN, these same actions take 4.2 sec, 3.1 sec and 1 sec, respectively.

Other than serving the dbase via the web, is there another way to serve this database in a faster way?

Richard

[Anatoli]

TCP will be faster, than AppleShare. Depends on Networking version and setup.

But I would not recommend going under 64k connection.

The only faster way is to open local databases with design and scripts and get just the data from shared database.

[RAP]

quote:

---

Originally posted by Anatoli:

TCP will be faster, than AppleShare. Depends on Networking version and setup.

But I would not recommend going under 64k connection.

The only faster way is to open local databases with design and scripts and get just the data from shared database.

---

[RAP]

quote:

---

Originally posted by Anatoli:

[qb]TCP will be faster, than AppleShare. Depends on Networking version and setup.

But I would not recommend going under 64k connection.

The only faster way is to open local databases with design and scripts and get just the data from shared database.

---

[/QB]

[Anatoli]

Design 1 database with fields, layouts, graphic etc.

In second database use no graphic and try both on your connection.

Change fields in the "nice" graphic database to hold values from the plain database -- you have nice db with fast connection to the second (remote) db.

Put on your first database related fields from second db.

By all possible combination you will find solution to your speed problems. You can call that "distributed database system".

Do you get the idea?