Excluding empty date field from portal

[Kevin Cheesman]

I have a main, sort of 'overview' form with a number of portals to show the progress of jobs through a production cycle. I realise I need TO's of my Jobs table to filter the different portals but what is the best way to exclude records that have no date in a particular field?

TIA

[Søren Dyhr]

You have delivered info a bit to meager to say much usefull about here, but perhaps Ugo's method makes some sense:

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

...that's the way I probaly would do it, but would require an auto id on the records in many table!

--sd

[Kevin Cheesman]

What I'm trying to do is display data in a portal where a certain date field is empty. As this is a despatch date, this field, the portal would then only show me just jobs than are still in progress.

[bcooney]

I would create a flag field, flag_InProgress_c, which would equal 1 if the job is InProgress (this must be a stored calc, result number). The definition of InProgress is up to you, but could be as simply as isempty (Date_Closed).

Then, the relationship to this portal would include a match of a constant 1 = flag_InProgress_c.

[Søren Dyhr]

Does it hurt to have record ID's in every table? I can't help seeing both globals as well as constant as a fix of the sort pushers facilitate a marked with.

It's in my humble opinion the pre fm7 way to do things when nothing else existed - when values didn't tunnel thru the relational "channels"!

The relational rule about primary keys it breaks, is this one:

[color:red]"Its values must uniquely and exclusively identify each record in the table"

--sd

ShowUncompleted.zip

Edited August 14, 2008 by Guest
at template might enlighten further

[Kevin Cheesman]

Thank for your help guys

[Søren Dyhr]

Well it can be done simpler with a y2k'ish kind of reasoning via a typecast exploiting that the entered date very well might be some 700000 days later than the recordID...

--sd

ShowUncompleted_y2k.zip