[FX.php List] Design for Locked Records?

[Dale Bengston]

Jonathan,

Happy new year!

What type of response do you get from FX if you try to modify a locked record? Do you get error 301 "Record is in use by another user"? Maybe you could trap for that and manage the expectations of your web users that they may need to try again later.

Dale

On Jan 5, 2010, at 5:55 PM, Jonathan Schwartz wrote:

> Any takers?
> 
> I'm developing a solution where the client employees are interacting with the same db that the online system uses.  It is possible that an office worker might be "in" a record while the online customer is trying to update.
> 
> What to do?
> 
> Error out?
> Try again?
> Send a message to the office worker?  (possible?)
> Save the data to another file?
> 
> Just looking for ideas.
> 
> J
> 
> 
> Happy New Year Folks,
> 
> Does anyone design for the instance where an fx.php transaction tries to update a record that is being used by a native FileMaker user, and thus is locked?
> 
> If so, how do you handle?
> 
> Thanks
> 
> J
> -- 
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-370-5011
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list
> -- 
> Jonathan Schwartz
> Exit 445 Group
> jonathan at exit445.com
> http://www.exit445.com
> 415-370-5011
> _______________________________________________
> FX.php_List mailing list
> FX.php_List at mail.iviking.org
> http://www.iviking.org/mailman/listinfo/fx.php_list