FM Speed issues solved for large databases

[carlz]

I wanted to share a discovery of mine. I run very large databases 380,000+ records and growing. We had a database that was terribly slow when creating new records. It would take 7-13 seconds to create a record. During the 7-13 seconds, it sent about 4 megabytes of information.

What was it sending?

Every unique primary ID of the database to the client... so the client can configure out if the record it made was unique or not...

What fixed it? I had to uncheck the check for "Unique" values in the field settings.

I think it's rediculous that something as keeping unqiue values is so poorly implemented not to mention poor FM backup implementation. This product isn't ready for businesses.

[Reed]

If the only field you need to check uniqueness for is the primary key field, then you don't need to have the unique validation on. Just use the autoenter serial option, and don't allow changes, and the value will be a unique PK.