![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I am trying to create a database that holds the following Client ID number Client Name Client Description Billing Notes (date, description, amount) The notes bit needs to be growing list of separate items consisting of three related fields. I started off thinking I could do this with a repeating field, but that wouldn't necessarily keep the three bits of information together and would also mean that the Client records that have very few Billing Notes would have a lot of wasted space since the repeating field would have to be set to a high number of repeats to accomodate those that have lots. Any ideas on the best way of achieving this? |
#3
| |||
| |||
|
|
In article <saramerriman-5E907A.11225323032010 (AT) news (DOT) individual.net>, Sara <saramerriman (AT) blueyonder (DOT) co.uk> wrote: I am trying to create a database that holds the following Client ID number Client Name Client Description Billing Notes (date, description, amount) The notes bit needs to be growing list of separate items consisting of three related fields. I started off thinking I could do this with a repeating field, but that wouldn't necessarily keep the three bits of information together and would also mean that the Client records that have very few Billing Notes would have a lot of wasted space since the repeating field would have to be set to a high number of repeats to accomodate those that have lots. Any ideas on the best way of achieving this? For the sake of other clueless FMP persons: I created another table which has the required fields for billing notes, plus a field for the Client ID number and linked the two tables' Client ID number entries. I could then insert a portal to display the records with the same Client ID number in the records in the 'main' database. I had to create a rather fugly script (attached to a button) to let users create a new entry in the second table, but it should do the basics of what I want. I'd still love to get any other ideas though. |
)
)
#4
| |||
| |||
|
|
"Sara" <saramerriman (AT) blueyonder (DOT) co.uk> wrote in message news:saramerriman-D397ED.14162223032010 (AT) news (DOT) individual.net... In article <saramerriman-5E907A.11225323032010 (AT) news (DOT) individual.net>, Sara <saramerriman (AT) blueyonder (DOT) co.uk> wrote: I am trying to create a database that holds the following Client ID number Client Name Client Description Billing Notes (date, description, amount) The notes bit needs to be growing list of separate items consisting of three related fields. I started off thinking I could do this with a repeating field, but that wouldn't necessarily keep the three bits of information together and would also mean that the Client records that have very few Billing Notes would have a lot of wasted space since the repeating field would have to be set to a high number of repeats to accomodate those that have lots. Any ideas on the best way of achieving this? For the sake of other clueless FMP persons: I created another table which has the required fields for billing notes, plus a field for the Client ID number and linked the two tables' Client ID number entries. I could then insert a portal to display the records with the same Client ID number in the records in the 'main' database. I had to create a rather fugly script (attached to a button) to let users create a new entry in the second table, but it should do the basics of what I want. I'd still love to get any other ideas though. You don't need a Script ("fugly" or otherwise). )If you set the Relationship to allow the creation of related records, then users can add new Notes using the blank row at the bottom of the Portal, and FileMaker will automatically take care of setting the appropriate Client ID. The only problem will be if the related records need extra data than is displayed in the Portal. Unfortunately the blank row is always at the bottom of the Portal. There are various ways around that, but from memory the easiest would be an "Add Note" Button with a Script that says: Go To Field [Relationship::RelatedField] Go To Portal Row [Last] Another way is to use a set of Global fields for the user to type in and then have the Button's Script transfer the data to a newly created Related Record. Helpful Harry ) |
![]() |
| Thread Tools | |
| Display Modes | |
| |