Hi all

This what I was wondering if it can be done in a portal or in FM.

We are required to track if a welder welded in a qualified welding process every six months.

A welder may have four or five qualified welding process at one time. So all of these process have to be used in this six monthe period. So each records for one welder for one process would look like this in the continuity log table

Record number one

Name: Hank Waldmann

WElding process GTAW

Last day welded: 1/2/2007

Record number two

Name: Hank Waldmann

Welding process FCAW

Last day welded 1/8/2007

Record number Three

Name: Hank Waldmann

Welding Preocess SAW

Last Day Welded: 1/10/2007

and so on.

There are fifty welders with Qualification in the continuity log table.

So the idea is to find the last day welded before the six months are up and that is no problem. WE perform a find on a date range and show the required welders in a list view layout.

I would like to show the records in a filtered portal but only one line per welder.

Example of list view

Hank Waldmann GTAW 1/2/2007

Hank Waldman FCAW 1/8/2007

Hank Waldmann SAW 1/10/2007

then the next welder and then the next welder.

Example of what I would like to do in the portal

outside of portal GTAW FCAW SAW

Hank Waldmann 1/2/2007 1/8/2007 1/10/2007

Adrian Walker 1/3/2007 1/9/2007 1/11/2007

can this be done?

I have done something similar to this for tracking our welder repair average but only in a list view and using two extra layouts but which is only printed every quater.

Thanks for the input in advance

Lionel

First off, do you need two tables instead of one, one for welders and one for their "accomplishments"

So for each welder do you need to show the last date for each type of welding - if so look at Ugo's method ... with conditional formatting would it then be easy to "redden" the near expiring.

Here is it count:

http://fmforums.com/forum/showpost.php?post/266487/

...but it could be changed just a little by sorting the relation from what Fenton calls _c_self_Criteria... reversely - because he by his unsorted picks the first, where we need to show the latest instead. We won't be needing any aggregate function just make the date shown.

--sd

Soren

thanks for the information and I have printed the information out but what is Ugo method?

Thanks

Lionel

Well it's what Fentons template shows, I could sometime tomorrow change it if you should wish, provided other participants here wouldn't jump in ad show what I mean ... it's pretty late here, need to eat before going to the Bowlingplace

--sd

soren

Thanks

Did not realize that wnat you were talking about.

I will look at the template.

Thanks

Lionel

Edited January 12, 200917 yr by Guest

Soren

Look at Fenton example and it sees close to what I would like to do but I am not good at complex relationship but I think that I have found a way to do what I want with a script.

Thanks for all the help

Lionel

Well i promised a template, basically have I done a bad job teaching by linking to a template you didn't get the gist of. However - since getting into safe haven by scripting is kind of a surrender because scripting often is a remedy for a poorly structured solution.

It's the synchronisation as such, where it goes wrong! By such as tagging the latest of each group is that many users in a networked solution might disturb each others found sets, unless it's a global field recieving the ID's for each record. But even so is it the vertical display of that will cause troubles. Further more is scripting the matter often something that takes some time to perform.

I have in my template shown both Ugo's method as well as Edoshins Crosstab technique ... plus a discovery made by Michael Horak, the undocumented behaviour of related summary fields! (which I just have tested if it have survived into fm10 as well - OK)

--sd

Welders.zip

Soren

basically have I done a bad job teaching by linking to a template you didn't get the gist of. However - since getting into safe haven by scripting is kind of a surrender because scripting often is a remedy for a poorly structured solution.

No, you have not done a bad job of teaching. Not all minds work a like and my mind work toward scripting instead of by relationship. I see how Ugo methods works and how it can be applied the the first process but not to the second and thrid process with only showing one welder name.

I have down loaded your template and will review it thoroughly and let you know how I made out.

Thanks for all the help Soren.

Lionel

Soren

The example is awesome. Never in my wildest dream that I would have thought that this could be done through a couple of relationship and a few calculation fields.

Thanks again.

Lionel

You're welcome!

In the above image have I made some guidance to where what happens!

--sd

Soren

Still studying but starting to understand your example of how you got there. Thanks very much again.

Lionel

Soren

One more request. I would like to have a portal that would show the maximum date of a date range. I have made a relationship called Continuity log and installed a portal but I am not there yet. I can do it with a find script but I was wondering if it can be done through a relationship without a find?

Example:

Date range

12/24/2008 to 1/30/2009

FCAW GTAW SAW

Hank 1/12/2009 1/14/2009 12/30/2008

Adrian 1/2/2009 1/28/2008 1/25/2009

Thanks for the help

I attached what I have done.

Lionel

welders.zip

Pretty easy, instead of the cartesian relation, use a dual criteria more or equal to lowest date and the other lower than the upper date. The match field is then not ID to ID but range to performance date.

I will first be able change your template tonight, due to a tight schedule today!

--sd

Soren

Thanks

Tried what you said but I still got something wrong because the welder show up on multiple lines instead of one line per welder

Lionel

Edited January 14, 200917 yr by Guest

Tried what you said but I still got something wrong because the welder show up on multiple lines instead of one line per welder

Well I spoke too hasty, is instead a combination of techniques used in tab 2 and 3 ... sorry for the confusion!

But before giving it a stab, must I be sure I get it right, you wish to portalize the ones with expired certificates?

Would it be only those exipirering certificates, perhaps a layout made in another tool telling what is required in this layout ... would get me closer to what you're after?

--sd

Soren

I want to thank you again for helping me with this.

I think I figured out almost everything. Got two of the three fields to display the dates so if you could, please look at the attached file to see why the third field is not displaying the date.

One more question,

I want to know if a "X" is put in a field called inactive and have this "X" installed in three other fields called inactive in different tables through a relationship

Thanks again

Lionel

c_welder.zip

Edited January 15, 200917 yr by Guest

I want to know if a "X" is put in a field called inactive and have this "X" installed in three other fields called inactive in different tables through a relationship

Well I'm too daft to get the meaning of this ... so what if I make you a small "food for thoughts" template?

--sd

Untitled.zip

Soren

Thanks for the template, will look at it.

Thanks again for your help in this manner.

Lionel

On second thoughts, the first one wasn't particular multi user'ish neither was it keeping the set from session to session, so here is a modification.

You might wonder why the scripting gets that comprehensive, but filemaker attempt to opposed to spread sheets to render as little as possible, the script is a measure to force the required refreshing through.

BTW is the CF used this:

http://www.briandunning.com/cf/39

--sd

XingMulti.zip

soren

Thanks for the time and effort and I will look at this example.

Lionel

Soren

I thought I had the date range relationship figure out but only one welder dates show up on both welder fields. I attached a file to help explain what I trying to do.

Thanks again

Lionel

welder.zip

You need to explain what you need in plain words, digesting your files is not getting me any nearer.

Is it a portal showing who is going to brush up on their skills to keep their certificates, and how does these expire and why?

A few look in you files shows me something else, why is the portalization required at all since the formal task is to make printouts of certificates. Portals and printouts are each others repellants, so for the task of summarizing or as here simple aggregating the last of an incident should genuine reporting task be observed instead of forcefull squeezing something into an unfortnate fitting metaphor.

...as well as:

http://filemakerlayouts.blogspot.com/2008/04/filemaker-merge-fields-explored.html

Seems both to be the two ignored skill sets really required, but which unfortunately have gotten sidetracked a propellerhead like me, since I didn't find the task too overwhelming as tasks to accomplish via portals.

In forums like this is stumbling near i sheer courtesy and and attempts to exhibit a measure of decorum, to avoid to criticise the reasoning behind a request. Sometimes is it next to impossible to get there, because the requester keeps the facts close to the body, with a poker attitude.

All repliers here needs the bigger picture, in order to give decent answers. Otherwise will all aims be of shotgun-type ... how can you control anything but the repliers urge by giving thrifty handouts of lumps, how can you direct the battle at all - chances are that the replier starts chasing own tail instead of being of any use at all.

--sd

Soren

I was struggling with similar set up today and stumbled across this post/sample.

I think you just cleared the sky in a cloudy brain, many thanks.

Olly

soren

I have learn something about FM relationship from you. Thanks for the U tube link and for all the help you have given me on this problem. Best wishes for a New Year.

Lionel

I was struggling with similar set up today and stumbled across this post/sample.

Which? ...after having being guessing severly, would it help to know what hit it on the nail!

--sd