Jump to content
Richmilnix

passing variables between table occurrences

Recommended Posts

My goal here is to write a database with tidier relationships than I've used in the past, so I'm intending to use discrete table occurrences of the same data. Here's the roadblock:

In layout 2_week_schedule, I have 14 portals that display a staff schedule (two weeks' worth) and can't be edited. My goal is that a logged-in administrator can click on the date field of any one of those fourteen days and go to a layout 1_day_schedule that is displaying the same information, though with more details and one day at a time.

The underlying table of each layout is the same, though the layouts are based on different TOs.

I wrote this with a script trigger in the date field in 2_week that fires a script to copy its value as date to variable $date, switch to the 1 day layout, and set the pertinent date field there to variable $date (and then commit).I don't know if it's my error, but I think of variables as being like my computer's clipboard - any value can be copied & pasted to/from. But the script fails with the message The operation could not be completed because the target is not part of a related table.

I did try a simple redundant relationship (connecting the two pertinent fields), but that was a hail Mary, and didn't do the trick anyway. Is there a better way to accomplish what I want? In short, I want administrator who's scrolling through the existing schedules to be able to look at any date where she wants to make a change, click on it, grab its contents, and be brought to a more flexible interface where its contents get inserted into a portal that will then show her the results.

This file is web-accessible, so I can post its address if it helps to see what I'm talking about.

Share this post


Link to post
Share on other sites
Posted (edited)
19 hours ago, Richmilnix said:

The underlying table of each layout is the same, though the layouts are based on different TOs

Why is this a good idea? It seems it only adds complexity (as demonstrated by your question).

 

19 hours ago, Richmilnix said:

the script fails with the message The operation could not be completed because the target is not part of a related table.

Apparently you are not setting the field of the TO of the layout you have moved to. If you started on a layout of TO X (the 2-week view) and then moved to a layout of TO Y (the daily view), make sure your Set Field[] step is targeting the local field Y::ViewDate, not the unrelated field X::ViewDate.

--
BTW, your mention of the need to commit records suggest that the dates are not global. They need to be, otherwise one user selecting a time slot to view selects it for all users.

Added: Also, since global fields are accessible from anywhere, without a relationship, this would also eliminate the error you're complaining about.

 

Edited by comment

Share this post


Link to post
Share on other sites
Posted (edited)

You know what, I have only myself to blame - years ago reading about Anchor-Buoy structure I Was really attracted to the notion of discrete TOs coupled by a slew of relationships - but each time I try to implement them I make sort of a hash of it. Thanks for your input.

Edited by Richmilnix
typo

Share this post


Link to post
Share on other sites
56 minutes ago, Richmilnix said:

the notion of discrete TOs 

You've mentioned that twice but it is not clear to me what you mean.  Is your goal to have just one TO per base table?  And if so, why?  What specific problem would that solve for you?  Or is an abstract notion?

Abstract notions is what gets a lot of us in trouble, premature optimization, unneeded modularity,... that kind of thing.

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, Richmilnix said:

years ago reading about Anchor-Buoy structure I Was really attracted to the notion of discrete TOs coupled by a slew of relationships

I am not really a fan of A/B, but even in that method the rule is that all layouts of a base table belong to a single TO (the "anchor" TO) of that table.

--
P.S. Please note the addition to my previous answer.

 

Edited by comment

Share this post


Link to post
Share on other sites

All right, let me try to answer without digging myself any deeper.

First of all, I'm not arguing with you guys. Clearly, I overcomplicated things. But since Wim asked what I was after:

I'm a part-time developer who only dives back into FMP every few years when I have a problem that needs solving. That means that I don't spend a lot of time thinking about logical schema. As my projects began to grow more sophisticated and more interrelated, I found that my relationship maps were sprawling - mostly because what had started off as a db hosting events was now also hosting staff schedules, and now was also incorporating POs and invoices, and everything seemed to be related to everything and my relationship graph looked like a child's drawing of a millipede cocktail party.

So in short I was trying to neaten things up. I'm still (I guess) a bit mystified about some of the complexities of relationships. Even after straightening out my separate TOs, I still have questions about passing variables, so I'll post back later about them.

Share this post


Link to post
Share on other sites
1 hour ago, Richmilnix said:

Even after straightening out my separate TOs, I still have questions about passing variables, so I'll post back later about them.

Passing variables is something you do between scripts and has nothing to do with TOs so there is some really fundamental confusion in your mind that needs to be cleared up, otherwise you'll come up with answers that don't fit the question :)

Share this post


Link to post
Share on other sites

You're right; I was conflating two issues (because I thought my variable trouble was stemming from my mixed-up TOs). Reframing my question in a new thread.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Who Viewed the Topic

    1 member has viewed this topic:
    Lape 
  • Similar Content

    • By Richmilnix
      For an inventory management database, I'd like my main screen to be able to accept pulls from three related databases:
      - Serialized (valuable tools, which I track and want back - the paintbrush);
      - Replenishable (cheap tools that I buy by the yard and if one gets left behind I don't care - the paint-mix sticks);
      - Perishable  (disposable tools that are left on the job site - the paint).
      These will handle their related requests differently. The serialized I'll be tracking properly to make sure we keep track; the latter two I'm looking for more like a system of 'tick marks' to help me know what we use on job sites.
      We print our barcodes. For ease of use, I'd like staff to scan into a single field in an interface that is smart enough to do the right thing based on a key digit in the barcode. So when I scan barcode 'S1234', my db knows to move it to the Serialized relation field; when I scan 'P1234,' it knows we're in Perishables.
      Looking for the elegant approach. My thought is that that central hot field (Scan_Here) will, when entered, store a variable and trigger a script built within the context of the related table, but I'm sometimes prone to reinventing wheels and doing stuff the long way, so I'm asking for suggestions / examples.
    • By JH Howland
      I have created an "opener" file called "OpenMP" that is located on the Windows Desktop.  Also, a global variable for the directory where the FMP14 files are located called "$$marinaDir" = "MarinaPro v17".
      When activated the launcher opens but does not open the target file using the following file path, "filewin:/C:/$$marinaDir/Marina.fmp12."  However if I substitute with the following, "filewin:/C:/MarinaPro v17/Marina.fmp12"; all is good.
      The script elements follow:
      #Create variable...
      Set Variable [$$marinaDir; Value: "MarinaPro v17"]
      #Start MarinaPro...
      Open File ["Marina"] (Marina File Path: filewin:/C:/$$marinaDir/Marina.fmp12)
      What am I missing?
    • By davidrichards
      I am having a tough time getting the set field by name script step to work and hoping someone can help me with this.
      I have a file of sales transactions over many years.  I have a related file for customers.  The customer file has counters for how many times a customer visits each year, how many suits, sportcoats, etc. they buy each year ( visits_2017, visits_2016, visits_2015, suit_count_2017, suit_count_2016, suit_count_2015 and so forth). I would like my script to evaluate the year of the transaction in sales and update the appropriate counter in customers.
      I have been unsuccessful in defining a variable and set field by name combination to accomplish this task.  Any recommendations?
    • By Richmilnix
      I'm reframing a question that I posted in a confusing way. Using variables seems so simple to me, but I know I'm missing something. I'll just post exactly what I'm trying to do so you guys can tell me why it isn't working.
      The project is a db that will handle shift schedules for employees. In the one-day view I'm looking at, the essential live field is a global date field called gDate_of_work. A portal is looking through to related records and returning a list of employees (from a table called staff_schedule_match), identified here by unique serials, who are scheduled to work that day. There is a second portal, located on the same layout, that is (correctly) showing a separate related list, of employees who are available to work on the day of the week.
      I, of course, want to be able to click on the name of an available employee and pass her serial number, along with the date in the global date field, to a new record in staff_schedule_match. In the distant past, I've sometimes solved this by opening layouts in offscreen windows and having extra fields dedicated to this data transaction, sometimes even by using the computer's clipboard (i.e. copy/paste).
      The script I'm trying to execute here goes:
      Set variable ($shift_add_nuid; employee's serial number from related record two) Set variable ($work_date; date displayed in this global date field) Freeze window Go to layout staff_schedule_match New Record Set Field (staff_schedule_match:nUID; $shift_add_nuid) Set Field (staff_schedule_match:StartDate; $work_date) Set Field (staff_schedule_match:EndDate; $work_date) Commit Record Go to layout (original) Refresh window Stepping through the script watching Data Viewer, I can see that the correct data is getting loaded into the variable values, but I can also see that the destination fields show up with an Unrelated table error. I don't understand why - I expected the behavior to be destination-agnostic, like my computer's clipboard, where if I copy some text in an email, I can paste it into a word processor or a browser or whatever.
    • By Asu
      Hello, I have a Case calculation that does not return what I expect
      wd1 = width of image in container1 , ht1 = height of image in container1
      wd2 = width of image in container2 , ht2 = height of image in container2
      A script would open up a popup window sized to the parameters of the image in the container. This is how it starts:
      Set Variable [ $contfield; Value:Get ( ScriptParameter ) ]  //which is the name of container1 or 2 which it gets correctly Set Variable [ $ht; Value:Case ( $contfield = Untitled::container1; Untitled::ht1; $contfield = Untitled::container2; Untitled::ht2; "ERROR") ] Set Variable [ $wd; Value:Case ( $contfield = Untitled::container1; Untitled::wd1; $contfield = Untitled::container2; Untitled::wd2; "ERROR") ]  The calculations return "ERROR". Which I don't understand as I would expect $ht/wd to be set to the corresponding numbers in ht1/2 and wd1/2. What am I doing wrong?
      Thanks
×

Important Information

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