April 11, 200223 yr Newbies Hello, I have a field that is set to a value list, values are : A B C D E F I want a summary field that will tell me across all records, how many A's there are, B's etc. I can not seem to figure out how to do this one. thanks
April 12, 200223 yr There are several ways to do this. The most important question is whether you want to print this count in a report or display it on a layout in browse mode. In a report, create a summary field defined as Count of (any field will do). Create a layout with a subsummary part defined as subsummary when sorted by (field name for field with "A", "B", etc.) For just this information, the layout might look like: Header Subsummary when sorted by (field name for field with "A", "B", etc.) Footer Before you print, sort by (field name for field with "A", "B", etc.). To display this information in browse mode, you will need to create two fields and a relationship for each possible value of your original field (I'll call it RecType). Create the fields: RecType (text) this is your original field with values A, B, etc. ValueA (calculation, text, indexed) = "A" ValueB (calculation, text, indexed) = "B" ValueC (calculation, text, indexed) = "C" ValueD (calculation, text, indexed) = "D" ValueE (calculation, text, indexed) = "E" ValueF (calculation, text, indexed) = "F" Create the relationships (with the same file): "Self by A" with ValueA <--> TypeRec "Self by B" with ValueB <--> TypeRec "Self by C" with ValueC <--> TypeRec "Self by D" with ValueD <--> TypeRec "Self by E" with ValueE <--> TypeRec "Self by F" with ValueF <--> TypeRec TotalA (calculation, number) = Count(Self by A::TypeRec) TotalB (calculation, number) = Count(Self by B::TypeRec) TotalC (calculation, number) = Count(Self by C::TypeRec) TotalD (calculation, number) = Count(Self by D::TypeRec) TotalE (calculation, number) = Count(Self by E::TypeRec) TotalF (calculation, number) = Count(Self by F::TypeRec) The "Total" field are what you want to place on a layout for your counts. -bd
Create an account or sign in to comment