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.

Strange Application/Memory Reference Error

Featured Replies

I'm having a strange problem with my opener files. For 95% of the users/computers it works fine. There is a seperate copy of the file on each desktop, it's not shared in any way. When some users open the file is gives them the following error:

"FileMaker Pro: FileMaker Pro.exe - Application Error : The instruction at "0x77805a10" referenced memory at "0x0021f000". The memory could not be "read".

Click on OK to terminate the program "

It's not a faulty install of FM Pro because different users logged in under the same PC can use it fine. It's not a privelage issue because one of the Admins here is having problems with it on his machine.

I have tried creating a new opener file on their specific machine. While it gives the error when you just launch that file directly from the desktop, you can open the file in FM pro, run the script manually, and it will work as it should.

The script consists of:

Allow user abort (off)

set error capture (on)

open(minimized, ...hostsfile...)

This script is set to run when the file is opened, like any other opener file.

It's also not OS specific, some W2k machines have problems, some XP machines have problems. Very odd! Any ideas?

  • Author

Thanks.

I know it's not a PC issue because some user accounts work on the local PC, others don't. Same with our terminal server, some user accounts work fine, others don't.

How are these files being served?

  • Author

Filemaker server 5.5

We've seen - previously there, now gone - printers toss up errors like the one you are seeing. Take a look in the Filemaker section of the Windows registry and you might see an odd or old printer associated with the troublesome user.

We have fixed the problem by wacking the user's Windows profile on the offending machine but be sure you copy all of the user's stuff first.

Good luck.

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.