FMPRO-L Archives

December 2012, Week 3

FMPRO-L@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Todd Geist <[log in to unmask]>
Reply To:
FileMaker Pro Discussions <[log in to unmask]>
Date:
Sat, 15 Dec 2012 15:00:06 -0800
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (933 bytes) , text/html (1551 bytes)
Hello Tami,


Tami Williams wrote:
> Or, is this a way to get around record locking.
No it is not.

The Parent record will still be locked.  There is no way to to stop the 
parent record from being opened and locked when you edit a child 
record.  This is a core principle in how FileMaker handles data.  I know 
that at times like this it seems like a pain in the ass, but it is 
actually A VERY GOOD THING :-)

If you want to use this kind of an interface, and many people do, you 
have to make sure that each user ( or machine ) has their own record to 
work off of.  This is often done by creating a record on login for each 
user ( or machine ).  This is why some people call the this table a 
"Session" table.  Each "session" gets it's own record in the Session table.

Hope that helps.


Todd


-- 
Todd Geist
geist interactive <http://www.geistinteractive.com>
805-419-9382
GoDraw <http://www.geistinteractive.com/godraw> - Draw on Photos with 
FileMaker Go



ATOM RSS1 RSS2