As a possible work around, try making sure the data entered inthe sibling table is commited before changing tabs.
Hi Phil... this seems to make no difference as it can strip data from more than one sibling table when it occurs. I will check today if closing then opening the database 'secures' the data before capturing the imagery.
I don't have an iPad and am only making generalized suggestions here. What I had in mind was simply performing the commit records step or clicking/tapping a blank area of your layout (which should commit the record) before attempting to capture a picture to see if that makes any difference.
Thank you for your posts.
I'm having a little difficulty understanding your exact steps. This is what I have done:
1. I created a few tables, with a main table "MAIN" linked to several child tables via a Number field named "ID".
2. In one of the child tables (named IMAGERY), i included a Container field.
3. In the MAIN table, I created a portal into IMAGERY via ID with the option to add records through the portal.
4. I created a button in the portal with a "Go to Field" script step for the Container field. (In FileMaker Pro, I had to use the Insert Picture command, but since that is not available in FileMaker Go, just the "Go to Field" script step invoikes the dialog box with the option to take a photo).
5. I make the file available on the network and access it via FileMaker Pro on an iPad 2.
6. I tap the button, a new record is created, I select the option to take a picture and save it to the Container field.
7. I switch to all of the different layouts for the other child tables. When I come back to the MAIN layout, the photo is still displayed in the Container field.
Let me know what I'm doing differently than you, and I'll try to replicate the problem here.
I use the INSERT FILE option... I'll try INSERT PICTURE and see if this solves the problem.