Instead of identifying the record by its RecordNumber, which changes on Find and Sort, identify the record by its primary key or other unique identifier. Question: How does your calculation determine which record number to go to from your original found set?
Sabenah K. Casey, Associate Court Clerk Jury Complex New York City Criminal Court 100 Centre Street Room 543 New York, New York 10013 TEL (646) 386-4580 [email protected] >>> Ron <[email protected]> 11:01 AM 12/22/08 >>> Will Go to Record by Calculation use the record key in a global? I thought it could only use the record number? Ron Carr -----Original Message----- From: FileMaker Pro Discussions [mailto:[email protected]] On Behalf Of Sabenah K. Casey Sent: Monday, December 22, 2008 10:50 AM To: [email protected] Subject: Re: Go to Record by Calc What about using a global variable that is set to the unique identifier of the record that would be in question? After the Find but before the Sort, g_Value would be set to the primary key for that record as part of the script or as a subscript. Sabenah K. Casey, Associate Court Clerk Jury Complex New York City Criminal Court 100 Centre Street Room 543 New York, New York 10013 TEL (646) 386-4580 [email protected] >>> Tim Mansour <[email protected]> 10:43 PM 12/21/08 >>> > I suppose that Go to Record by Calculation based on calculation > where you use RecordNumber, that the RecordNumber changes when one > does a Sort on records, e.g., whereas a record that is at position 4 > in the unsorted situation, could be at position 1076 in a sorted > situation. > > Is this correct? Yes it is. Go To Record is based on the found set and hence is affected by find and sort parameters. -- Tim Mansour <[email protected]>
