< ? php include( '../top1.php' ); ?> Error Codes: FileMaker Error 101 - Record is missing

Software Venture Consulting

FileMaker Pro downloads & Resources
FileMaker Custom Functions
FileMaker Web Viewer Examples
FileMaker Pro & Lasso Consulting
Training
FileMaker Books
FileMaker Articles
FileMaker Error Reference

Free Web Tools
Free FileMaker Tools

Personal Pages
Videos
Adventures
Links

Shopping Cart
Shopping Cart

Search:

Free Newsletter
Signup


Contact


Privacy Policy



FileMaker is a registered trademark of FileMaker, Inc. in the U.S. and other countries.

 

 Reference: FileMaker Error 101

FileMaker Error 101 : Record is missing

FileMaker Error Codes

Lasso Error Codes

MySQL Error Codes

Windows System Errors


About this database
This is a free public resource. It is unmoderated and operates on the "public virtue" system. I hope you find it useful!

User Contributed Notes

2005-12-05 15:00:35
Brian Dunning
BrianDunning.com http://www.briandunning.com

You'll often get this in a web application (Lasso, etc.) when you try to update or delete a record by specifying an invalid -RecordID or -KeyValue.

This is my note and I want to edit it | Report an inappropriate comment

2009-05-14 10:03:17
Thomas Andrews
Soliant Consulting http://www.soliantconsulting.com

This can also occur when trying to set a related-record field when:

(1) The related record does not exist, and
(2) The relationship does not allow creating the related record from the parent table

This is my note and I want to edit it | Report an inappropriate comment

2011-04-01 12:19:18
Aaron Koenes

This can also occur when trying to delete a related record through in incomplete relationship. This is often encountered when a relationship is based solely on global fields.

For example, if you have a relationship that uses global fields and no records in the parent table, then having a value in the global fields will complete the relationship and retrieve related records to display in a portal, but trying to delete a portal row will give this error.

Adding a single record to your parent table will allow the record to be deleted.

This is my note and I want to edit it | Report an inappropriate comment

2012-02-15 11:08:26
Alex Taylor

This error will occur if you are using the Script Step 'Go to Next Record,' and you are already on the last record of the found set.

If you have not specified 'Exit after last' in this script step, error 101 will be thrown when you attempt to use this step while on the last record of a found set.

This is my note and I want to edit it | Report an inappropriate comment

2014-05-14 04:21:33
Jack James
Surreal Road Ltd http://www.surrealroad.com

This will occur on Filemaker Go if you try to access a Global field (e.g. with insert from device) that's not directly linked from the current table occurrence.

This is my note and I want to edit it | Report an inappropriate comment

2016-04-28 12:38:22
Brian Crockett

Found a problem the reverse of Aaron Koenes mentioned above.

If you're trying to create a record via a relationship the parent table needs to have at least 1 record even if if that table has only global fields.

This is my note and I want to edit it | Report an inappropriate comment

2017-04-22 22:25:16
Orlando Ferraiuolo

This happens also when you use Go To Related Record using "match found set" and the FIRST parent record has no related records.
If there are no related records for the whole set, it returns error 401 (No matching records).

So the correct way to test for no related records is:
- GTRR Match current record only: test for error 101
- GTRR Match found set: test for error 401

This is my note and I want to edit it | Report an inappropriate comment

+ Add your own note
< ? php include( '../bottom.ssi' ); ?>