Import records can copy the current found set of records in one table into new records in another table. If you manipulate your found set so that your quote is the only record in the found set, this method can be used to copy your quote to an invoice table.
But I'd carefully consider keeping quotes and invoices in the same table. It's also possible to lable your records in this table as quotes or invoices and you can use duplicate record to generate an invoice record from a given quote record.
With both methods, if you have a related line items table for your quote and your invoice, you'll also need to copy them as well, but these will likely need updating to match to the correct duplicated record.
Would you say it makes more sense to have one table (Quotes/Invoices) rather than two (Quotes table, Invoices Table).
I had originally considered this as I know I could in most cases have a field which has either Quote or Invoice as the value. This would cut down on 'traffic' as the records wouldn't be cross-table, I would effectively be copying a record within the same table.
Actually, reading back what I've written, I think I may have answered my own question.. I think a single table for both would be more sensible.. would you agree Phil?
It's why I suggested that option. It allows you to use one layout for both quotes and invoices--saving you the added effort of maintaining one layout for each.
Of course your user needs for quotes and invoices may be sufficiently different that you end up with two layouts even with the unified table....
A unified table can also make some reports much simpler to create--such as a report that lists invoices and quotes in the same report.
Thanks Phil... as ever, quality advice!! Very much appreciated.