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 5886 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted (edited)

Have you saved a copy compressed?

what is the Field, calculation, container, text, number, etc.?

Is there a relationship involved?

Does the field contain data?

Lee

Edited by Guest
forgot the data part
Posted

so, have you tried saving a compressed copy and seeing if this is still a problem?

How many records are in this file?

Posted

Have you notice any other problems with the file.

This might be a sign of corruption. There used to be an Article by [color:red]gdurniak Here, but it doesn't seem to work anymore. Read this information found in the Help File Link, and review the post in the Damage and Corrupt Topic Link

HTH

Lee

Posted (edited)

As my database has grown in size so has the time it takes to delete a field in a table. Everything else seems to work fairly quickly.

Any ideas?

One of the very strange things that has been found to be related to slow field deletes: all your variable names must be lower case. Not $SomeVariable and not $someVariable but $somevariable.

Sounds crazy but the problem has been repeatedly tested and lower case fixes it.

Another thing I will sometimes do is NOT delete the field but just turn it into a global, zDeleted01, etc. This can also help if you have import scripts or if you want to compare file versions. You just look at the fields in creation order and you can see where the changes occurred.

Edited by Guest

This topic is 5886 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.