Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×
The Claris Museum: The Vault of FileMaker Antiquities at Claris Engage 2025! ×

This topic is 8108 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

Hi,

I've never seen this before. I have a database, lets call it MainDB, that's related to 4 others. To create a record in one of the 4 child files you click a button, a script runs to determine if you've already created a child related to the current MainDB record. If you have it tells you to try one of the other three children. If you haven't created a related record you're taken to the file where you can create a new record. Ok so far, and this has always worked in the past. Until today.

I can create related records in the first three child files but for some reason when I click on the 4 button, I get this message: "Sorry, there is not enough memory to complete this operation". Then when I click the "ok" button, I get "The previous script step "End If" could not be completed because of an error. Do you wish to continue this script?" It doesn't matter if I click Yes or Cancel. Same results, nothing happens. What gives? I am doing an update to an existing database and so I only have one record in the MainDB and 1 each in the first 3 related child files. I'm running FMP 6.0v3 on a Mac G4 with 640mb of RAM (OS 10.2). There is no way I don't have enough memory. Anyone else run into this? Any ideas of whats going wrong here?

Help me please?

Thanks

Joe confused.gif

Posted

The times I have run into this (on Win platform only) it was my fault. If you messed with the script lately, and inadventently changed a Perform Script step to call itself, FM barfs.

Posted

Right what is likely happening is the there is some kind of recursive script calling and eventually it fills the available memory. It is actually the script being loaded over and over again that is causing the memory overflow

Posted

You guys had it exactly right. Thanks for the heads up. I had looked over the script and didn't originally see any problems. Plus, it had been working fine up until just recently. After reading your posts I went back and looked at the script again and found the offender sticking out like a sore thumb.

Thanks again.

Joe

This topic is 8108 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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