repetitions and serial numbers

[posternutbag]

Hello!

I have a table that contains 3 text fields (med, qty, directions) and they can all repeat up to 8 times in a record. So, something like this:

 

MED(1)  QTY(1)  DIRECTIONS(1)

MED(2)  QTY(2)  DIRECTIONS(2)

MED(3)  QTY(3)  DIRECTIONS(3)

etc.

 

I would like to have a 4th column/field that contains a serial number for each of those lines.  I don't mind if each record gets 8 serial numbers, so long as I can hide the extra ones.  How do I do this?  I have a separate layout for the form where I can just hide the extra serial numbers- if I could have help with that though too that would be great.

 

Thanks

[Lee Smith]

Hi Posternutbag, and welcome to the Forums,

 

Why are you using repeating fields instead of related records?

This topic has been moved from "FileMaker Pro 10" to "Calculation Engine (Define Fields)".

 

The General Topic Area for the different versions is for the decussion of the Tools, Functions and Features that were new new in that vesion of FileMaker, and not for asking how to questions.

 

If you have any questions about this action, please contact me by Private Message.

 

Lee

[LaRetta]

Hi PosterNutBag, 

 

As Lee suggests, you have a less-than-optimum structure and you cannot get what you want as it is.  You need a TABLE with the following fields:

 

ID (auto-enter serial number ... see options on the field)

Medium (text)

Quantity (number )

Directions (text )

fk (number of this parent table's ID ... this connects this single parent record to its multiple child records you will create

 

With this structure, you can have as many items as you wish and they each have their own serial.  Your current structure also would make it extremely difficult to generate reporting, search and summarise ... for example:

 

If Med(1) was wanted in a report which was sub-summaries by Quantity and that RECORD had 25 in Med(1) and 30 in Med(2), that single record could not appear in both sub-summary parts (for 25 and for 30).  There are many such examples why your structure should be changed now.  You will find records as opposed to fields much easier to work with.