Hey All!,

I hope this is the right forum for this topic...

Currently I've got a relational DB used for time sheets/invoicing that's modeled after the sample that ships with FM. Employees enter their activity, room/equipment used and time spent on that activity which creates a line item record in a separate file via a portal. We bill for both the employee and the room/equipment used so I'm trying to figure out the best way to split each record in the line item DB into two individual records, one for the employee and one for the room/equipment. Any conceptual or practical advice on this topic will be greatly appreciated.

Thanks...

If you are tracking by room/equipment as well, you could have a RoomDB file that is related to the same line item file as the Employees. If I understyand your question, the line item data for both employees and room will be the same (start time, end time, project description, etc...), so no need to duplicate, just include a key to relate it to Room file.

HTH

-Raz

I think he means he wants two line items to show up on an invoice. You need to either create a script in line items that duplicates the record and then modifies the data in both the duplicate and the original, or... script the creation of line item records from the data entry side, or... if you create line items via portal, train the data entry people to make two entries. Or use two portals (i.e., define another relationship to line items so that only items matching "employee" show up in one portal, and those matching "room" show up in the other).

Ah yes, quite.

Thanks a bunch guys. I was actually able to get the desired resut from Raz's suggestion to another post.