This topic is 2602 days old. Please don't post here. Open a new topic instead.
Wondering whether this is one of Filemakers limitation and/or there are any ways round it.
i have a portal which displays my related records to a customer . These records are split down to two sections (Two options) i had created a slider that on slide 1 it displays option 1 and on slide two option two.
However the slider only seams to show up on the top portal row.
i would appreciate if anyone could explain me if this is not possible or something was just set out wrong.
I've just started using MirrorSync to sync our production iPads with our FileMaker server, and overall I am thrilled with the functionality. I do have one weird little issue, though, that I'm hoping someone can help me with.
I have a table called Step Intervals, and none of the records from this table appear on the iPads after sync. It's not for any of the obvious reasons: I do have the Step intervals table checked in the MirrorSync setup, all the fields I want synced are on the sync layout, etc.
However the table itself contains a self-join. Without getting into a ton of extraneous detail, it's meant to record the ideal interval between two steps of my production process happening (stored in the Steps table). So Steps Interval looks something like this:
Step Interval ID
Where the beginning and end fields both contain foreign keys for different instances of the Steps table.
I did try adding a layout for the second Steps instance to my MirrorSync setup, but got the message "Node FileMaker Server has dependencies from other nodes, but it was never added to the NodeConfiguration with addGroup". So I know I'm doing something wrong, but if the solution is in the documentation I'm missing it.
Any pointers much appreciated!
Change of Ownership
I have written a database which manages my dog breeding activities, I am not great with databases - it was never my day job - and I have have hit a snag with which I would be grateful for some help.
I have a three tables;
One contains all the dog's (puppy's) details that I need (Dog's Unique ID No., DoB, Sex, `Sire, Dam, etc...).
One contains all the Owner's details ( Owner's Unique ID No., Name, Address, Phone Nos, Emails address, etc...
One Join Table which uses the Dog's Unique ID No. and the Owner Unique ID No. as foreign keys and links the two tables together using a DogOwner Unique ID No.
This works fine when I sell a puppy or dog and I have no problem with assigning more than one dog to an owner (some owners have several of my dogs) but...
Sometimes a new home doesn't work out and I buy the puppy or dog back and resell it to different owner.
What I can't work out is how I can keep records of all the owners (active or not) whilst transferring a dog from one to the other, I don't want to delete an owner as I need to keep a record who has owned my dogs in the past but I also need to produce a file of information for the new owner using layouts for Insurance Cover Notes, Microchipping, Registrations etc.
i have tried deleting the DogOwner Unique ID No. from the record (which I thought was the only link between dog and owner) but somehow all layouts still display the original owner.
I just can't get the database to recognise the new owners - the old owner's data is displayed on every layout - including the new Agreement of Sale which I need to send to the new owner.
It is rather like a serial numbered product being returned and resold so there must be a way of doing it.
I have just installed (yesterday) FMP 16 - upgrading from FMP 12, running on a Mac.
Sorry if I haven't explained this very well.
Hi, pulling my hair out here!
I would like FileMaker to build a setlist based on which staff member knows what song.
I have a database of songs and a database of players
I have a join table that links these - it looks like this:
I want to do take the above information and say something like this...
Find: STA01 and STA05
Constrain find to all matching songs.
*using the info above that would be...
That would give me a setlist of songs that BOTH STA01 and STA05 know. I tried to do this through a portal and failed miserably - I couldn't work out a calculation that would give me both - on reading some documentation it seems that you can only find "1 set" of criteria through a portal relationship?
So I tried using a script - "Find matching records" after the initial "Find of STA01 & STA05" but that only returns 1 "set" of matching records... not multiple records that all match...? If you get what I mean.
I also tried using the "!" to find duplicates but that does not work either.
Please could someone point me in the right direction - I am I even thinking about it the correct way!?
In my database of weekly music charts (FMPro14) there are 4 linked tables:
[Hits] - list of the hit singles
[Entries] - list of different entries, remixes, reissues
[Runs] - list of chart placings for every week
[Dates] - list of dates of the weekly charts
<idHits> index field
<Title> text field
<idEntries> index field
<Title> text field
<idHits_fk> number field, a foreign key which links [Hits] table with [Entries] table
[Runs] contains fields as below:
<idRuns> index field
<Place> number field, position on the chart
<LastWeek> number field, last week position
<idDates_fk> number field, a foreign key which links [Dates] table with [Runs] table
<Title> text field, title of a single
<Name> text field, name of the artists
<idDates> index field
<Date> date field
Relations are as follows.
[Hits] & [Entries] are linked by the relation:
Hits.<idHits> = Entries.<idHits_fk>
[Entries] & [Runs] are linked by the relation:
Entries.<idHits> = Runs.<idEntries_fk>
[Dates] & [Runs] are linked by the relation:
Dates.<idDates> = Runs.<idDates_fk>
Two years ago, on this forum, with a Consultant help, I have defined the self-join as:
Runs::idEntries_fk = Runs 2::idEntries_fk
Runs::idDates_fk ≥ Runs 2::idDates_fk
where Runs 2 is a new occurrence of the Runs table. Then define a calculation field (result is Number) = Count ( Runs 2::idRuns )
This will return the number of times the entry has appeared in the Runs table before (and including) the current week.
So this allows counting chart weeks for every record in [Entries].
Now, I’d like to also count TOTAL number of weeks, for [Hits], not [Entries], something like:
Runs.<Place>; Runs.<LastWeek>; Entries.<Title>, TotalWeeksCount for main record in [Hits]
Example. Let’s say there is a hit single titled „Purple Rain”. Looking at its chart history we should get something like:
Purple Rain - original entry - 10.10.1984 - 10 (0) 1 week
Purple Rain - original entry - 17.10.1984 - 8 (10) 2 weeks
Purple Rain - original entry - 14.12.1984 - 43 (33) 10 weeks
— out of chart —
Purple Rain - re-entry - 08.07.2008 - 56 (Null) 11 weeks *** 11 weeks, NOT 1st week of this new entry! ***
Purple Rain - re-entry - 15.07.2008 - 48 (56) 12 weeks
How can I get such results? Help needed, thanks!
Who Viewed the Topic1 member has viewed this topic:arni