For repeating a field... i know that if you use the Last(field) it will repeat something. But is there a function that will clear a field if nothing is in it?

So say on one layout you don't enter something and on another layout that keeps a history of that field, that it doesn't even show up on the layout because it is empty...? There has to be a simple way.

Edited October 4, 200520 yr by Guest

ANYONE!?!?!?!?!?

Please explain how you have you your database set up. Which layouts from which table?

I have two layouts. One is an Incoming Inspection Log, the other is a History of Inspection.

Right now it is set up so that you can search for anything from Part Numbers, Vendors, Customers, Date Received... and so on. When we have something come in and it is rejected upon inspection because usually it was assymbled wrong or damaged, we write up an Inspection Report (which is part of the first layout).

I want to set up my layout so that when I search for say... a history of a supplier, on that history layout a section will show of how many rejections we had for a paticular day and so on... but if there were no rejections, I don't want an empty field showing up. I want to eliminate empty space. I don't want the field of "description of rejected" material to show up on the history layout if there were no rejections to describe. I need a caliculation field that will clear something, rather than repeat it.

Is this possible?

I have two layouts. One is an Incoming Inspection Log, the other is a History of Inspection.

Right now it is set up so that you can search for anything from Part Numbers, Vendors, Customers, Date Received... and so on. When we have something come in and it is rejected upon inspection because usually it was assymbled wrong or damaged, we write up an Inspection Report (which is part of the first layout).

I want to set up my layout so that when I search for say... a history of a supplier, on that history layout a section will show of how many rejections we had for a paticular day and so on... but if there were no rejections, I don't want an empty field showing up. I want to eliminate empty space. I don't want the field of "description of rejected" material to show up on the history layout if there were no rejections to describe. I need a caliculation field that will clear something, rather than repeat it.

Is this possible?

try:

Rejected = case(isempty(Rejected);"";Rejected)

my filemaker does not have a "rejected" field... it won't let me copy and paste it either. Do you know what version that may be for?

Substitute your field name for 'Rejected'.

I don't have a "Rejected" function

i tried renaming it and putting in

Rejected = case(isempty(Rejected);"";Rejected)

but no luck

anyone with suggestions?

Assuming that you are using a field "Rejected" to store the number of rejected materials. Breezer meant to say:

you create a calculation field cRejected and give the following formula in the calculation:

case(isempty(Rejected),"",Rejected)

Keep cRejected on the layout.

Case ( IsEmpty (Description 1 Copy), result1 [ , test2 , result2 , default result]... )

Description 1 Copy is my origional field to enter stuff... i need a result of something like, clear(description 1)

or something like that... i need to clear it, delete it, erase it... make it so the copy is where the origional data is entered (layout #1)... and on layout #2 (the history layout) the similar field (descrition 1 copy) is erased, cleared or invisible if no data is entered on layout #1

Copy and paste the below line in your calculation:

Case(isEmpty(Description 1 Copy),"",Description 1 Copy)

Keep the calculation field on layout#1 and layout#2

Is this a lost cause?

will show of how many rejections we had for a paticular day and so on... but if there were no rejections

Yes I kind of think that you're barking up the wrong tree - So this is actually a statistical issue, this does unfortunatly for you rule out repeaters and urge you into a proper relational structure ...which by the way solves you issue with clearing fields as well.

But the whole issue by going relational is that each entry could trig a timestamp, which could be used as key for another relation.

This other relation holds a layout that filter the logging based both on type and the timestamp in a multicriteria portal ...so searches in reality are substituted by entering or choosing criterias from a dropdownlist.

--sd

What is the name of your field? I assumed your field name is called REJECTED.

Use the name of your field instead of 'Rejected' which I used for demo purposes. Note that REJECTED is not a function but a FIELD name.

Make the substitution or attach your file and I will fix it for you.