 | |
Where has "Exit Record" gone?
comp.databases.filemaker comp.databases.filemaker
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Where has "Exit Record" gone? -
07-31-2005
, 06:21 AM
#2
| |||
| |||
|
|
Hi FileMaker people - I admit to being slow to learn and implement new versions, but I'm finally using V.7 and beginning to like it, despite its much-discussed intricacies and awkwardnesses. When my script moves from a parent record to a set of child records, and manipulates some values before returning, I find that I get a "can't edit these records, they are in use" type message. I can see that this is because with the parent record locked for editing and the child records reflected in a portal, FMPro locks them too. I used to use the good old "Exit Record" script step to avoid record locking problems like this, but I don't see it in V.7 ScriptMaker. Could someone please tell me what has taken its place? Or a new method to avoid the problem? Many thanks in advance - James |
Matt
#3
| |||
| |||
|
|
James wrote: Hi FileMaker people - I admit to being slow to learn and implement new versions, but I'm finally using V.7 and beginning to like it, despite its much-discussed intricacies and awkwardnesses. When my script moves from a parent record to a set of child records, and manipulates some values before returning, I find that I get a "can't edit these records, they are in use" type message. I can see that this is because with the parent record locked for editing and the child records reflected in a portal, FMPro locks them too. I used to use the good old "Exit Record" script step to avoid record locking problems like this, but I don't see it in V.7 ScriptMaker. Could someone please tell me what has taken its place? Or a new method to avoid the problem? Many thanks in advance - James They just changed the name. See "Commit Records/Requests". |
than it ever used to be! I find i need orders of magnitude more of them
in FM7 than i needed previously. In my latest FM6- 7 conversion, most of
the bugs that occured were solved by adding Commit Records in the right
places.
(Rebuilding the solution in FM7 is coming, but getting the existing
system running under 7 is priority 1).
#4
| |||
| |||
|
|
James wrote: Hi FileMaker people - I admit to being slow to learn and implement new versions, but I'm finally using V.7 and beginning to like it, despite its much-discussed intricacies and awkwardnesses. When my script moves from a parent record to a set of child records, and manipulates some values before returning, I find that I get a "can't edit these records, they are in use" type message. I can see that this is because with the parent record locked for editing and the child records reflected in a portal, FMPro locks them too. I used to use the good old "Exit Record" script step to avoid record locking problems like this, but I don't see it in V.7 ScriptMaker. Could someone please tell me what has taken its place? Or a new method to avoid the problem? Many thanks in advance - James They just changed the name. See "Commit Records/Requests". Matt |
And there we go. Many thanks for your prompt reply, problem solved!
James
#5
| |||
| |||
|
|
In article <OE3He.5333$GN5.5014@trndny08>, I'm (AT) Witz (DOT) end says... James wrote: Hi FileMaker people - I admit to being slow to learn and implement new versions, but I'm finally using V.7 and beginning to like it, despite its much-discussed intricacies and awkwardnesses. When my script moves from a parent record to a set of child records, and manipulates some values before returning, I find that I get a "can't edit these records, they are in use" type message. I can see that this is because with the parent record locked for editing and the child records reflected in a portal, FMPro locks them too. I used to use the good old "Exit Record" script step to avoid record locking problems like this, but I don't see it in V.7 ScriptMaker. Could someone please tell me what has taken its place? Or a new method to avoid the problem? Many thanks in advance - James They just changed the name. See "Commit Records/Requests". Its also MUCH MUCH MUCH MUCH MUCH MUCH MUCH.... [...] more important than it ever used to be! I find i need orders of magnitude more of them in FM7 than i needed previously. In my latest FM6- 7 conversion, most of the bugs that occured were solved by adding Commit Records in the right places. (Rebuilding the solution in FM7 is coming, but getting the existing system running under 7 is priority 1). |
Thankfully, I'm building my first large FM7 solution from scratch. I
will certainly need to keep this in mind, though, when I have to convert
old solutions to FM7 as I inevitably will. Thanks for your input.
James
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.