relationships with continunity log

[The Big Bear]

Hi all

Been trying to figure on how to do this for a couple months now and as you can see I am not to good on relationship.

I attached three jpeg file that I hope explain what I want to accomplish.

After verifing that a welder has welded in a welding process that he has been quialified for, I log the date in a continunity file. This need is done for ever six months of employment.

The file continunity example show how each individual record is recorded in the file.

The continunity have example is how is print on the form that is posted in the foreman office.

The continunity want is how I would like it to print.

Thanks in advance.

 

Lionel

 

 

[doughemi]

Something like this?

 

 

Welder Cert.fmp12.zip

 

Uses a separate portal for each process.

 

 

[The Big Bear]

thanks for the reply

I cannot open zips files at this moment.

I tried using a separate portal for each welding process and that work perfectly for display purpose only but I would like to print a report as shown in the third example.

 

Lionel

[doughemi]

Just put the portals for each process side by side on the report layout.

[The Big Bear]

my past experience with portal print has not been good. Portals only print what you can see on the screen. Some of these welders have at least 60 entries for each welding process.

 

thanks

 

Lionel

[Fitch]

Gather each column of dates into a text field or global variable. Then use a virtual table to display the results. Sorry I don't have time right now to go into details.

[The Big Bear]

Tom

Thanks for the information.

I read up on virtual table but still not sure what they are or how to create them.

If you would go into a more detail on how to gather the dates and make a virtual I would greatly appericate that.

 

Thanks for all your help in the past.

 

Lionel

[Fitch]

A virtual list is essentially this:

Create a table that has a calculated field that looks like:

GetValue( myList ; Get(RecordNumber) )

 

"myList" can be either a global variable ( $$myList ) or a field -- typically a global field, since it has to be a field that every record in the table can see. Of course "myList" is just a placeholder, you can name it whatever you like.

 

In your case you'd want one field for SMAW, one for GTAW, etc.

first field: GetValue( $$SMAWdates; Get(RecordNumber) )

2nd field: GetValue( $$GTAWdates ; Get(RecordNumber) )

etc.

 

With me so far?

 

Now you need a script to set the variables, from the context of the person record:

Set Variable( $$SMAWdates; List( related::SMAW dates ) )

Set Variable( $$GTAWdates; List( related::GTAW dates ) )

etc.

 

OK, so you've created your table with the five calculated fields, you've created your script to set the five variables, now just create as many records in the table as you think might be needed, say 1000. The last step of your script can find just the records with data, and you're ready to print.

 

Hope that helps.

[The Big Bear]

Tom

I have two tables one with the welding information called "Continunity" and another table called " LIST" with the script in the calculating fields. Is this the right setup?

I do not understand how the calculating fields known what record number to capture as the way I have is setup thet do not capture any recorder number.

I understand how is it done but cannot did it to work.

 

I made five calculating fields in the TABLE "LIST" as follows: Gobal, = GETVALUE ($$smadates;get(recordnumber))

 

Then I wrote a looping script in the table "LIST" as follows: Set Variable ($$ smadate; value(continunity::SMAW dates))

for all five calculation fields

I am not sure on what field or fields that I should make the relationship on.

 

no informatin is shown on the list table

I do not have have winzip so i cannot post a copy of the files.

 

 

Thanks for all the past help

 

Lionel

[Fitch]

Hmmm, I assumed you had a table for welders that was related to the dates table. If all you have is one table you can still use my method using a self-join, or if you're on FileMaker 12 you can use ExecuteSQL to get the date lists. I think the latter would be best, since I see that we also need to account for the "type" field. Are you on FM12?

 

It is possible to use a looping script as you've done to populate the variables, but you'd do that in the original table, not LIST. The LIST table is just for viewing/printing. By the way, I'd suggest naming the table something else, to avoid confusion with FileMaker's list function.

 

It looks like your calculation would only capture one date. We want it to be a list of dates.It should look something like:

Set Variable[ $$smadates ; List( ($$smadates ; continunity::SMAW date ) ]

 

That will append each date as you loop through the records.

[The Big Bear]

Tom

I am Sorry for not having the FM edition.

I am using FM10 advance.

Now you have me curoius about the two tables.

The continunity table has the welder ID and the Welding process and the date Welded and the expiration date as fields.

I do have a table that has the welder information as Name, ID number, and Stamp but this table is not connected the the continunity table.

 

I think I have a data structural problem.

The continunity log file has only one date field called 'DATE WELDED:"

There is another field called process that captures the welding process (i.e. GTAw, SMAW, FCAW, etc.)

To make each record unique, I have a field that combine the ID number, the Date welded as a number and the welding process.(i.e. 2345 SMAW 768902)

 

That could be the problem.

How would you suggest that I construct the continunity log table.

 

Thanks for the information, will give it a whril.

 

Lionel