2 different invoices but 1 serial number

[concrete]

I need 2 different sorts of invoices, each depending on a differten database of products. So far no problems

but the seial number needs to keep counting independently

meaning:

1 invoice a

2 invoice a

3 invoice b

4 invoice a

...

now my 2 kinds of invoices count seperatly

hope this is making any sence

[danjacoby]

My own personal invoice system requires two different types of invoice -- I just use two different layouts in the same file. It's pretty obvious which layout I need for each invoice (there's certain data that shows up in one, but not in the other), but just to make sure, I have a "Print" button that checks to make sure I'm in the correct layout before printing each invoice (I only print one at a time, being as I am just one of me -- what I call a very small business).

[LiveOak]

This is really pretty easy. Create a field "InvoiceType", which will be either "a" or "b". Create a self-relationship with InvoiceType matching InvoiceType in the same file (I'll call it SelfByType). Create a "new invoice" script with the step

New Record

SetField(InvoiceNumber, Max(SelfByType::InvoiceNumber) + 1)

-bd

[concrete]

OK you've lost me,

can you explain a little bit more.

thx

concrete

[danjacoby]

Oak, I could be wrong, but I think the question involves one run of serial numbers covering two different types of invoices; your solution seems to create two different lists of serial numbers, one for each type of invoice.

I'll stand by my idea -- one file with two layouts, one for each type of invoice. At least, until someone comes up with a better idea.