All files/tables in this discussion are fmp12 using FM 17 and both files are opened when initiating the app. "logging" is opened as the primary file and "claims" is opened as an external data source.
I have a table called "newclaim" in "logging" which contains mailing address information including a USPS zip code. I have a table called "lu_ZipCode" in "claims". There is a relationship set between "newclaim" and "zipcode" on a field called "COID" (company ID). This field is automatically populated in both tables with "DCSI". This is an old method (used in Fm6) of establishing a simple relationship so that global fields can be used to pass parameters into scripts for zip code lookup and verification.
In the parent script (in "logging") I set the related field "lu_ZipCode::_gZipCode" with (for ex) "12345" with the intent of calling a subscript in "claims" then using "12345" to do the lookup. However when the subscript is called the "_gZipCode" field is empty. As a workaround I called the subscript passing the "12345" as a parameter which of course works as one may expect. After setting the parameter to a local variable in the subscript I'm able to do the lookup then populate the global fields "lu_ZipCode::_gCity" and "lu_ZipCode::_gState" while still in the "claims" file. Yep, sure enough when I go back to the parent file the global fields I just populated are empty.
It's worth pointing out here that prior to yesterday "zipcode" was a separate file and the methods described above worked like a charm. This effort is being put forth to consolidate this old FM6 solution with 40+ files into just a few files. I imported "zipcode" into the "claims" file then copied and modified the scripts anticipating that this would be a quick little project to get rid of one more file.
I know there are better methods (ie JSON) to get this done and I will probably go that route. At the same time I'm left scratching my head on why this tried and true method doesn't work. Why would global fields I can populate from one side of the relationship not be populated when viewed from the other side?
I recently amended a db from an old Lynda course, controlling shore excursions for river cruise ships. For my limited expertise (I am still a rookie at the very best) the construction is somewhat complex as there is many vessels, different routes, different charterers and consequently different shore excursion programs and prices. In some cases the shore excursion program of different vessels and operators is similar but not the same and so on.
I have 7 different tables partly related (pls see graph attached):
For every journey ::customers and ::trip are assigned a tour code and date (“tour code” is not unique as journeys repeat themselves during the season, “Tour Code” in conjunction with “Date” is unique)
Every tour operator/vessel has many trips on every journey. All table occurences and fields are uniquely defined by unique id.
Now I want to create an opening layout reflecting all relevant cruise information such as passenger list from ::customer and ::trip (shore excursions) for the specific journey, as well as other information in text fields.
But I seem to be unable to get the right relationship and layout setups together. I tried all possible relations and layout setup combination but nothing worked so far.
On the same layout I was able to either retrieve the passenger list from ::customer for each journey or the offered shore excursion (trip) list from ::trip but not both together on one layout.
What is it, I am doing wrong? Any ideas are appreciated
By Randy Bennett
Yes, I did say iPhone 5 -
I have a small database i created that has a few portals on different layouts - Everything works fine on my Mac, fine on my iPhone X, even fine on my iPad mini
However, I need it to also work on an old iPhone 5 and the portal data is just blank - nothing. In fact, I really ONLY need it to work on this old iPhone 5 (This particular database will go to a music festival to be used by several other people and I can't give them my iPhone)
I have another layout with different portals that are working on the iPhone 5 - but not this main screen.
I have made sure that all of my fields are small and inside the portal. - So, I am stuck as to why? BTW - It is Filemaker Go 126.96.36.1996 (The latest version that I can install on an iPhone 5)
By cat traveller
on a file accessed via filemaker Go 17, I am using a scripted navigation to move records up and down in a portal that is inside a popover.
This has worked in filemaker 12 like a charm and also works on a filemaker client. The records smoothly move up and down the list.
However in Filemaker Go, the portal follows every move of the script as if it is not aware of the freeze portal.
EG the down button is to move the record one record further down inside the filtered and sorted portal (like so)
This is the script.
- freeze window and go to portal
- go to first line of portal and loop through the portal until I hit the record to move
- go to next line and give the position field the value of my record to be moved
- go to line above and give the position field the value of my record +1
- commit record and refresh portal via an x join
- go to last line of the portal
- go to the line of position of my record to be moved.
Would anyone be aware of this issue or know a workaround to stop the portal from flickering?
Thanks so much