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.

Featured Replies

I have just discovered that a particular database we're hosting on our FMSA11 box (Windows Server 2003) has developed an appalling response time for XML-based web calls since migrating to this server. It worked fine when it was on our old server (FMSA8 on OS X Server).

We're hosting over 70 other databases, many of them also publishing data to the web (I'm using FX.php), and this is the only file exhibiting this slowness. And by slowness, I mean over 15 seconds to return data from a table that has a single record and only 6 fields.

No errors are reported anywhere, it's just really slow. I managed to isolate the problem to this file by rebuilding this one particular simple table into another file, and it performs fine from the new file. That's only one tiny part of the database though, and I use the rest too, so I can't just rebuild it all.

I have tried cloning it, optimising it, renaming it, etc, but nothing makes any difference, and I can't figure out what's going on! It works fine when being opened from FileMaker 9 or 10 clients.

Help!

Kev

  • Author

Does anybody have any idea what might be causing this slowness on just one database?

Kev

No - but have you turned your attention to that the file might be corrupt?

http://fmdiff.com/fm/filecorruption.html?session=ti5eri8j2894mq4ak9pmu4hpnjs5agjq

--sd

  • Author

I have indeed. It works without any problem at all from within the FileMaker client app, but I optimised it anyway (using Save As...smaller copy). I even used the 'Recover' option, but neither action made any difference.

On both of our FMSA11 boxes, 2 different versions of the file exhibit the same issue. So I fired up our old FMSA8 box, which still had an earlier version of the file on it, and it showed no problems with web-based XML data transfer. Frustrating!

Anyway, in the end, the guy who built the original file has built a cut-down version from scratch, just to interact with the web, and it's working fine.

Kev

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.