I have viewed many tutorials and asked many developers to help me get to what I have already.  What I have not asked is the following question:  How do I populate my portal?

 

Ok, here's what I have.

 

An Attendance Solution that has three tables:

 

NAME:

_kp_name_id

name

enable

 

DATE:

_kp_date_id

_kf_name_id

_kf_status_id

date

 

STATUS:

_kp_status_id

status

 

 

They are joined by the obvious keys.

 

Lets say that the NAME table has four records:

 

Bill          Enable

Mary       Enable

Steve

Laura      Enable

 

 

 

What I am trying to do is get all of the names that are enabled in the NAME table to appear EVERY time in a portal under the DATE table.  (Is this my first issue?  Which layout view and table should my main and portal be based upon?)  AND I also want the field status, from the STATUS table, to appear next to their names (as a radio-buttoned value list).  AND I want this to be the case EVERY time I create a new Date record.

 

So for example, I want the following:

 

Record 1:

 

DATE:  12/24/2012

 

Bill            Present     Sick     Work     Travelling     School     Other

Mary         Present     Sick     Work     Travelling     School     Other

Laura       Present     Sick     Work     Travelling     School     Other

 

 

Record 2:

 

DATE:  12/25/2012

 

Bill            Present     Sick     Work     Travelling     School     Other

Mary         Present     Sick     Work     Travelling     School     Other

Laura       Present     Sick     Work     Travelling     School     Other

 

 

Record 3:

 

DATE:  12/26/2012

 

Bill            Present     Sick     Work     Travelling     School     Other

Mary         Present     Sick     Work     Travelling     School     Other

Laura       Present     Sick     Work     Travelling     School     Other

 

 

 

I want this to appear EVERY time.

 

So, I ask, is this a filtered portal issue?  A scripting issue?  Will someone please be kind enough to help me through this?

Here's a sample file of how I'd design the system based on your stated requirements. I question the need for a Date table. Also, I would use a popup menu, not a radio select (but I like to save room on a layout).

 

I think this is best attacked from the context of a found set of active people. Work flow would be to find active people and take attendance.

 

hth, 

Barbara

Attendance.fmp12.zip

Barbara,

 

Thank you for responding and for providing the sample file.  As I am not a developer by trade, I want to take the time to learn this correctly and reverse-engineer what you have shown.  I like the direction you have gone in and I will work with it in list view to see how it looks with ~150 names.

 

My hope is to have a new clean portal record show each time a new date or time is initiated.(This is the purpose, I think, for the date table).  I see how your solution drops down to the next portal row, I was just hoping to eliminate, especially in list view with ~150 names, the need to scroll.  Each new record will be date driven.

 

Thank you and I will be providing feedback soon.  (Holidays are demanding with 2 kids and one on the way!)

Jason

OK, Jason. Let me know when you have more questions. Again, date tables are rarely needed.