As an afterthought, one reason you might not want to do it this way is that this
system could potentially reuse deleted group ID numbers if they're deleted "off the
top". Only an issue if recycled numbers are.
At 01:53 PM 11/29/00 -0800, you wrote:
>Sounds like a great solution.
>
>If you're curious, though, I think you could do it without having a "counter" field
>at all. Using the relationship All Names, which is a self-join relationship to every
>record in the names file, your script could use only one Set Field script:
> Set Field ( "GroupID" , " Max ( All Names::GroupID ) + 1 " )
>This should give one greater than the greatest group ID currently in existence.
>Haven't tested it, but I think it should work. Might be slower than your solution on
>large datasets, however.
>
>HTH,
>Matt
>
>
>At 12:31 PM 11/28/00 -0500, you wrote:
>>Thanks Thomas / Bob for the Advice!
>>
>>Here's what I did to solve the problem. Created a regular number field,
>>"GroupCount" in the setup file (since it only has one record) "GroupCount"
>>and then just referenced that field in my previous script.
>>
>>Andrea Barnhart
>>Reliacom CSD
>>www.reliacom.org
>>(202) 797-9735 x351
>>-----Original Message-----
>>From: Thomas Mokwa [mailto:[EMAIL PROTECTED]]
>>Sent: Tuesday, November 28, 2000 11:49 AM
>>To: Andrea Barnhart; [EMAIL PROTECTED]
>>Subject: Re: [SUPPORT] global field question
>>
>>
>>A thing to remember is that globals are only global locally! In a
>>network environment each user has their own globals. What I think you
>>need is a regular field in a file that has only one record. This way
>>the field could be accessed by any user and increased for all users
>>and retained on restart.
>>
>>I hope this helps. Please feel free to contact me if I wasn't clear.
>>
>>Regards,
>>
>>Thomas
>>
>>
>>
>>>Hello all those Filemaker experts out there,
>>>
>>>I have a problem that I hope you can help me solve. The basic requirement
>>is
>>>to link certain name records by a group id. I have created a global field
>>>"gGroupCount" and a number field "GroupID" I then have a script which
>>>creates a groupid by
>>> 1) Set Field ["gGroupCount","gGroupCount +1"]
>>>2) Set Field ["GroupID","gGroupCount"]
>>>
>>>This script works perfectly on a stand-alone version of Filemaker. (keeping
>>>track of the current group id and then adding 1 to create the next id).
>>>However when running on Filemaker server, whenever Ebase is closed and
>>>restarted, the global gGroupCount is reset; therefore not storing the
>>>previous group id.
>>>
>>>What is the correct way for storing a global variable across Server? Or is
>>>there a better way to create a unique number "on the fly"?
>>>
>>>Any help would be greatly appreciated!!
>>>
>>>Andrea Barnhart
>>>Reliacom CSD
>>>www.reliacom.org
>>>(202) 797-9735 x351
>>
>>--
>>____________________________________________________
>>THOMAS MOKWA
>>CG Software - Simply Useable Solutions
>>http://www.chickengirl.com
>>[EMAIL PROTECTED]
>>FAX: 419.730.9842
>>phone: 912.441-4064
>>
>>
>Matthew Scholtz
>Evaluator and IS Coordinator
>Health Initiatives For Youth (HIFY)
>www.hify.com
>
>
