Jump to content

danek

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About danek

  • Rank
    novice
  1. If a database is created with Advanced, can it be used (custom functions and all) on the regular version of FileMaker Pro? I think I will just do all my "loop" iterations by hand for now; it's not a big deal in this case. Thanks. (I tried to get it to work by doing a Calculation Repetition, but this ended up making my field a repeating field, which wasn't exactly a desired effect.) Thanks guys.
  2. Wow, that was REALLY easy. And no need for a join table, either. (What is a join table? Sounds like it might be useful to know for the future.) I just created a new table with two fields, Attribute UID (serial, autogenerated, not modifiable) and Attribute Name. Then I made my value list based off of Attribute UID, also displaying values from Attribute Name, and only displaying values from Attribute Name. Made a checkbox thingy and it worked like a charm. Only "gotcha" was that I had to add a bunch of leading zeroes to the serial number for Attribute UID. Otherwise, searching for "1"
  3. I like where you are going with this approach. I will have to read up on join tables. Thank you.
  4. That's a good idea. My only question is, if there are multiple search terms, how do I get the script to do the matching?
  5. Hi all, Is it possible to do a loop within a calculation (in Define Fields) OR to call a user-defined script from within a calculation? Each record has a set of related records. I want to define a calculation field displaying a particular related record if and only if it meets other criteria as well. Right now I have a calculation which looks really ugly (I am inexperienced with FileMaker scripting please don't yell at me!): If (GetNthRecord(Foo::Bar;1) = "Criterion"; GetNthRecord(Foo::Foo;1); "") & If (GetNthRecord(Foo::Bar;2) = "Criterion"; GetNthRecord(Foo::Fo
  6. OK a little bit of background here: I have a database that I did some time ago, where each record in one of the tables had a set of attributes, which were represented by a field displayed as checkboxes. This worked fine and well for some time, until the users decided they kept needing to add more attributes to the value list, causing problems during finds. Allow me to illustrate by example: suppose there was an attribute "Foo" which later received extensions to "Foo 2" and "Foo 3". If the user wanted to search for all records with attribute "Foo", all the records that had attributes
  7. (here's a screenshot of my relationships graph, btw...)
  8. I had the EXACT same problem, and I actually came up with the same solution myself after much head-scratching... (I came on here to see if anybody had any better ideas, and found this post.) In my case I have a table of "people" who can each take various "roles" ... there are 5 different "roles" and so I created five different instances of the "people" table... Then I realized that showing all of the "people" in each drop-down menu, instead of just whichever ones are appropriate for a particular "role" seemed silly, and tried to figure out a way to limit the value lists. Short versio
  9. That did the trick. You answered my other question, too (using different fields for setting/defining a relationship.) Thanks so much!
  10. Hi everybody! New around here. I have a database which has a couple of tables, and records that tie in to other tables based on a name field relationship. Problem is, if you change the name on a record (to correct a typo or for whatever other reason) it breaks the relationship with all the records in other tables using that name. To try and work around this problem, I gave each record a unique serial number that automatically gets generated when the record is created. This number does not appear on any layout, so it can't be changed accidentally. Currently this fix makes things less
  11. Hi everybody! New here - quick question which I'm sure is asked a lot, but I tried searching under "list view wrap" "list view row height" and a bunch of other queries, but can't find the answer: Is there a way to set up a layout so that in list view, if the contents of a field are longer than the column permits, the field displayed/printed will automatically get as tall as it needs to to accomodate the data? Basically, the goal is to have each record take up one line if possible, and if any particular field (free-form notes, for example) exceeds the width available, then the re
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.