together? Find a common link between all your data sources. It seem
tblTxtJournal should have a customer ID and link it to the
qeyNameAddressBlock.
Have extensive experience in developing accounting software. I would
put a copy of your customer address in your invoice history file. At
the time of the invoice, the address was this. If you change their
address, change the customer master, the old invoices should print with
the old address, the new invoices should have the new address.
> >From a design view in a query, can you link your queries and tables
> together? Find a common link between all your data sources. It seem
> tblTxtJournal should have a customer ID and link it to the
> qeyNameAddressBlock.
Yes, but my main question was regarding the syntax of the SQL statement:
SELECT [this], [that], [otherThing]
FROM qryThis, qryThat, tblOtherThing
Which I assume is perfectly fine (since it works), but I'm curious if this
is something peculiar to Jet - or is it acceptable SQL grammar which will
also work with other databases, such as MS SQL Server, Oracle?
> Have extensive experience in developing accounting software. I would
> put a copy of your customer address in your invoice history file. At
> the time of the invoice, the address was this. If you change their
> address, change the customer master, the old invoices should print with
> the old address, the new invoices should have the new address.
Good advice, to be sure, and that's exactly how it works:
All addresses are stored in a separate table. Each customer record can have
any number of addresses, one of which is selected as the primary, or billing
address. Invoices are generated dynamically (using the selected address),
automatically converted to PDF and emailed, and a hyperlink to the pdf file
is automatically inserted into another table which is displayed in a subform
datasheet. So old invoices are a click away and will show whatever address
was selected when the invoice was created.