Hi Vicky, At the risk of igniting a Religious Argument, I suggest your co-opt the Expense object for your booking form needs, as it:
supports the natural 1:many relationship you describe
can be further extended using custom data
would minimize your custom data maintenance in several ways (e.g. reuse the same dropdown on each expense row, easily aggregate multiple rows in reports, etc.)
We've used this technique several times to provide quoting, estimating, and invoicing solutions. Regards, Doug Den Hoed - AtAppStore Got Skills? Lend a hand!
https://community.workfront.com/participate/unanswered-threads