Me: Hmm... I need to store some information while I'm looping through records, but I don't want to act on this info until after I'm done looping. A local variable should do the trick.
FileMaker: wats a variable?
Me: Um. It's a symbol that can store values for a... wait, what? For serious?
FileMaker: oooh! I can store things! i haz fields for storing things!
Me: You mean columns?
FileMaker: no fields. fields r for storing things.
Me: Okay fine, fields. But fields are meant to hold data specific to the given record. I want to store information that isn't directly related to any record, and only for the duration of the script.
FileMaker: um um ummmm... oh! i noe! global field! :D
Me: Come again?
FileMaker: field haz same value for all records. u set value in dis record, and u get same value inn dat recorde.
Me: Really? All I'm looking for is a simple temporary place to store a value. Instead, you want me to go into the database schema (kicking everyone out of the DB), add in a new column. and update every record. All for what essentially acts as a global variable that will only be used by my one script? Are you kidding me?
FileMaker: *beaming* im so smrt!
Me: *facepalm*
---
Yes, newer versions of FileMaker understand variables. But this is what I get to work with, and it won't be changing any time soon. It's a little sad that FileMaker went the route of "global fields" before going for variables >.>
September 26, 2011
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment