Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Access speed to FMP5 db over dial up

Featured Replies

  • Newbies

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

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.

  • Author
  • Newbies

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.

  • Author
  • Newbies

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]

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?

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.