Howdy,

I have held out posting here, hoping to come up with the answer myself, but I am finding that I am going around in circles! Could someone please nudge me in the correct direction?

Although this is not an "Invoicing" solution, the analogy works and is one that many are familiar with.

The Scenario:

- User creates pre-populated invoices in advance, using any number of available products, and places them on the invoice is a particular sequence.

- Each product may appear on any invoice, but only once.

- Each invoice is unique and once created, is not able to be modified; if changes are required, a new invoice is created with the modifications.

So far, so good Now comes the "fun" part ... using these invoices ... this is where I am "stuck"

For this example, let's call this the "Checkout" phase:

- new Checkout record created

- Customer selected from Customer list

- Clerk selected from Clerk list

- Pre-populated Invoice selected from Pre-populated Invoice list

- "voila" ... there are all the "Line Items" from that particular invoice and in the correct sequence

- now it's just entering the "quantity" for each line item

What I am thinking (and I know that's a dangerous thing!) is that when the Pre-populated Invoice is selected from the list, a script will be run to copy the line items from the selected invoice to the line items in the "checkout lines" table. If so, i think I can muddle through creating that script (if not, I'll be back ) But I was wondering if there may be a way to do this through a relationship some how, or perhaps a different "structure" altogether.

Thanks in advance!

Lyle

Although this is not an "Invoicing" solution, the analogy works

In my experience, an analogy like that never works and it always comes down to "yes, but my situation is different".

I am going to make an "analogy" myself and suggest you look at:

http://fmforums.com/forum/topic/79864-prevent-changes-from-affecting-previous-records/page__st__20__p__372263#entry372263

:) Actually, in this particular case, the "analogy" does work, so let's just say that this IS an Invoicing app

In your example, the Relationships are "pretty much" what I have, and as expected, a script will be required to copy the values from the Invoice (Recipes) to the Checkout (Batches).

If I understand your process, you have a "template" that consist of an entity ---< items this is a library of item and it's children locked together for end user to apply or associate at check out with the customer / clerk / date of event.

at checkout they can choose one or more template(s) each with their own set of children - at which point clerk can only modify the qty for the items.

The end result is checkout is your primary parent entity with all the items associated?

@Ocean West - yes, what you describe is it exactly, except they can choose only one "template" per "checkout"

@comment - the "Add New Batch" script in your example worked perfectly! ... thank you so very much for your "analogy"

... mind you, I am now going to have to have a beer or three to "compensate" for transposing your example terms for my own! LOL

... mind you, I am now going to have to have a beer or three to "compensate" for transposing your example terms for my own! LOL

Better you than me... :getlost: