Jump to content

Grundly

Members
  • Content Count

    55
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Grundly

  • Rank
    member

Profile Information

  • Gender
    Female

FileMaker Experience

  • Skill Level
    Intermediate
  • FM Application
    16 Advanced

Platform Environment

  • OS Platform
    Mac
  • OS Version
    Sierra

FileMaker Partner

  • Certification
    13
    14

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello folks I am experiencing a peculiar behaviour, which is creating a user case problem, in a solution that is utilizing the Data Separation Model and WebDirect. I need to know if this behavior is normal, a bug, or if my implementation is incorrect. I've got an interface file and a data file. Each file has two Privilege Sets defined (in addition to [Full Access]); call them Floor and Manager. Floor has very restricted access, and Manager has more liberal access (but no where near Full Access). Scenario 1) I've made a script in the interface file which performs a re-login. A us
  2. Yes, after some additional testing, I've run into similar shortcoming in that solution, unfortunately. In your example, we would have wanted Melanie to also become related now to all 5 of Jane's other relatives, but that does not happen, Melanie is just left with Jane only instead of Jane and all of Jane's relatives. The structure in efen's file is the same structure I have right now in my real file. Not sure if this can be further enhanced via script, or if a change in structure is needed. At a loss, but feels like we are closer than before.
  3. Thanks folks you've been helpful. Efen, you got it, that file you created hits the mark. It looks like it was not trivial to create, so thank you for taking the time to put together such a thorough example. I like how the loop works. That's totally the piece I was missing. From this logic you've laid out, I should be able to adapt it to fit into the existing solution. Perfect, THANKS!
  4. I'm sorry if you are unable to understand my problem, I may not have explained it well enough. Would anyone ELSE like to take a stab at my problem? Please don't reply if all you want to do is talk about how good someone is. Only reply with technical answers about my problem. Thanks.
  5. Hello folks! Setup: Our graph looks like this: People >> FamilyMember >> People. The People table has a name field and a primary kp_PeopleID field. The FamilyMember table has but two fields: kf_PeopleID and kf_FamilyMemberID. The first relationship predicates are: People::kp_PeopleID = FamilyMember::kf_PeopleID. The second relationship predicates are: FamilyMember::kf_FamilyMamberID = People::kp_PeopleID. We have a portal on People layout, that looks at FamilyMember (and the second People table occurrence also, to grab their names). This is all fine and well to specify othe
  6. Comment, sounds like a good solution. I'll have to make sure the revised layout stays 'sorted' no-matter-what, but otherwise, close enough. Thanks again. Should serve the need quite well!
  7. Ah! That must be it then, thank you! Browse mode is in fact needed. I wonder if anyone has sent that to FileMaker INC as a feature request yet. Seems to me like.. when specifying Portal details, instead of only accepting an integer for the number of rows, allow us to enter a formula as well if we want to. And 'somehow' make Body aware of that option too. Probably opening up a nasty can of worms by doing that maybe. Thanks for taking the time to look into it!
  8. Laretta thank you Could I trouble you for a tiny demo file? I am unable to get that to work, I get no action at all. I've double and triple checked but I must be missing something still... Food.fmp12 Food.fmp12.zip
  9. Greetings FileMakers! Is it possible to have a Body part as well as a Portal within that body part both resize, dynamically, based upon the number of records within that portal, within certain pre-defined bounds? For example: I have a table of Foods (in database speak, not in the literal sense). The Foods table has a child table called Ingredients. We show the Ingredients via a portal on the Foods layout. The Foods layout is Browsed in List View. The Body part is, say, 150 pixels tall. Within that, we stuff a little 140-pixel-tall portal showing a few rows. We could define, say,
  10. Quick question... How about using $$globalVars there in place of hard-coding? Any problems you can forsee using that approach? Thanks
  11. Excellent information, Comment. I shall try to implement this, thank you. If I get it working, I'll post the new file up here for anyone who wants to see. (Perhaps I should .zip it next time?)
  12. What I have: • A table of Animal. Four records in this example. Three fields: a primary ID (number), a Name (text), and Quantity (number). TheQuantity number field's contents gets changed by users at various, random intervals. • A table of Snapshots. Twenty records in this example. Four fields: a primary ID (number), a foreign key (for Animal), Date, and Quantity. • A script that runs once every 24 hours (perhaps from Server). The script simply looks at the current state of each record in the Animal table (Quantity), then goes to the Snapshots table, and cr
  13. Perfect, this works great! Produces the sub-summary's record IDs in the form of a return-separated list, which is exactly what I needed. This is so much faster and cleaner. Thank you very much!
  14. 1. I don't fully understand the question. I'll attempt to answer: There are records present representing all three Types. The sub summary layout is sorted by Type. Thus in my hypothetical example, you will end up with three sub summary sections when sorted by Type, each with some records in them. One sub summary section for Type "Paper", one sub summary section for Type "Glass" and one sub summary section for Type "Plastic". This is already built and works as expected, nothing tricky, nothing unusual. 2. The purpose is to have a list of IDs, stored in a variable in a script (or placed
  15. I've got a Subsummary layout. The layout is based upon the table, lets call it "Materials". The subsummary part is sorted-by the field "Type". Type can have say, one of three possible values in it: Glass, Paper, Plastic. When we sort this layout, we get subsummaries by the types, Glass, Paper, and Plastic, as expected. There's a script that performs some Finds, based on user-entered criteria, to narrow down that list. What I need to do now is have a script gather the IDs of only the records under, say, Paper. And only Paper. Suppose three records are showing under Paper, I want those thre
×
×
  • Create New...

Important Information

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