Hi,

I have a table set up right now that consists of records that are individual jobs we do for customers. I partial bill several of these jobs every other month and am wondering if it's possible to create a related table specifically for partial bills for these individual jobs/records. I'm hoping this will then enable me to create as many partial bills for each job/record as I like. Somehow I'd like to set it up such that from Record/Job# 1, I can simply click a button that says "Partial Bill" and it will bring up a related table where "Job #1" is automatically pulled in and then I can enter the data needed to do the billing. I want the Job# field to be the field that triggers the rest of my lookup fields, which I would then slightly modify to do the partial billing.

Currently the table is set up such that each partial bill for a job is a duplicate of the record with a letter added on (i.e. partial bill 1 = Job #123, partial bill 2 = Job #123a, partial bill 3 = Job #123b, etc.). I think it'll be cleaner to be able to have a related table that specifically keeps track of these partial bills. Let me know if more clarification is needed and thank you for any help!

I take it for granted that invoicing the same orderline twice, perhaps is desired ... but isn't sustainable business practice. So some sort of dwindling these away is the key issue to pulling this off, which there isn't particular signs of in you present model ... alright there is an old template of John Mark Osbourne which goes under the name of Serialize By Category, which originates back to 1995 and FM3 - But meanwhile has the tool as such been revolutionized into to lean mean relational tool - which could be exploited.

I have here made at template showing how I think I would deal with it, based on a free interpretation of what you have specified - please ask if something is somewhat unclear!

--sd

P_artial.zip

Hmmm....this looks like something I can work with. Thank you so much!