You could have the two compent fields beside each other and then add them together in a calculation field.
You could have a script trigger on the field (or a button beside it) that offers the user a Custom Dialogue with two entry fields (can be globals, of course) where you collect the Family and Amount, then you join them and post the result to the field.
Use three fields. 1st field is first part of inupit, 2nd field is second part, and then 3rd field is a calculation field to combined first and second field. The calculation would be field1 & "-" & field2
That was also my idea at first, but I figured that there might be a way to use two input boxes for one field! The reason behind that thinking is to reduce the number of fields in a certain table being that I am creating a database to register printed questioners, which have more than 20 questions with a similar input!
Now if You do the math, if I use the method we all thought of, it will have more than 70 fields just for those questions, and there are around 90 more different questions... So You get the picture!
In a table of 100s of fields, you are talking about saving 2?
If I assume you have a universal global text or number field already available, then the custom dialogue saves you those additional two fields.
You didn’t understand, I will save 20 or 30 times the 2 fields You have mentioned! I have 24 questions in the form with the exactly the same input data! That’s why I wanted to make it 24 fields instead of 48 or more!
Any more info on the custom dialogue?
I have 24 questions in the form with the exactly the same input data!
These should be 24 related records with one question per record. That will reduce the number of field definitions far more than doing what you wanted--which won't work anyway.
See this thread for more on this concept: Need aid on generating a report from a survey layout.
What more information do you want?
When there is multiple entires for the same information it is usually an indication that a parent-child relationship should be set up. Although I don't really understand your table arrangements, as you say.
Edit: sorry, posted before I saw Phil's comment.
I detect slight misunderstanding, probably due to me not being able to explain correctly what I wanted (sorry, not a native English speaker)! So I think that an image will describe better what have I wanted to achieve!
This is a cutout of a actual form, as it looks on paper, and these 3 are just the first out of 24 similar question having 3 or more answers, so now You see what I meant by 60 or more fields.
It won't be "60 or more fields" if you design your database as I have recommended, it will be just 3 fields. Each question should be a separate record. Find the link I posted and take a look. What you describe is a kind of "survey" and the link I posted describes a possible set of tables and relationships for such a use of FileMaker.
Once again, thank You so much!