< ? php include( '../top1.php' ); ?> Error Codes: FileMaker Error 102 - Field 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 102

FileMaker Error 102 : Field 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-02-01 07:49:13
Brian Dunning
BrianDunning.com http://www.briandunning.com/

This generally means that you're trying to set or reference a field that has since been deleted. Check your script for <Field Missing>.

You probably shouldn't be getting this in a web app - you'd probably get the application server's error code instead. But it depends on what you're using. Don't use FileMaker scripts in a web app!

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

2007-11-19 10:08:40
Jerry Salem

You will get this error using CWP if you change the name of a field in Filemaker and don't update the xsl

Jerry

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

2010-03-24 10:47:47
E.J. Sexton
TourTech Systems, Inc. http://www.tourtools.com/

This occurred for me in CWP when I tried to update a field that was in a portal. As soon as I removed the field from the portal, the issue was fixed.

Also in CWP, trying to edit a related field in a portal will result in this error. However, you can edit a related field as long as it is not in a portal.

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

2011-02-23 15:29:27
Stephen B.

I had this same issue with CWP PHP on FileMaker Pro 11. I found out that my issue was that in PHP Site Assistant I had a different layout selected for the edit and confirmation pages. These different pages had different fields present and therefore I believed caused the issue.

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

2013-05-15 21:10:39
Christiaan van Minnen

This error can also happen when you have (unwisely) named your field in a way Filemaker cannot always understand. We had a field which could be read from a portal but NOT edited, just because someone decided to shorten the field's name and end it with a dot.

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

2015-10-16 07:59:00
Mike Beargie
MainSpring, Inc. http://www.gomainspring.com

This can happen when using an "Insert " script step, like Insert File, and the target container field is not on the layout. Make sure your target field is on the current layout when using the insert step.

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

2015-12-09 14:02:02
Nick G

If you add an Insert step to a script when a layout with another context is open, the script will throw this error even when running from the correct context/layout. To fix, ensure the correct layout is showing when editing the script.

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

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