You could, but you need to think what advantages that would give you. If it is likely that the same address will be associated with different subjects, yes. If the address is unique, more or less, then I wouldn't. You need to understand normalisation, but you can choose how far you go. I would consider it perfectly acceptable to embed the address in the subject record, but not all in one field.Maybe use an autonumber-table for each adress and use the autonumber in the main table?
One table. You need two fields in your main table to hold the PK of the invoice address and the PK of the delivery address. This tells you which is which.Yes.. it would be likely that up to 100 records would have the same adresses. So i think an autonumber-table would make sense. I dont need the ability to search for any of these, just want it to display in a certain form. The invoice and delivery-adress would often be the same, yes. But not allways, so i guess i DO need two seperate tables?
When this is stored it should be an ability to search for earlier used adresses.
This is standard behaviour of a combo box.Is there an ability in access to make a full name pup up when they begin typing something that is allready in the database? like intellisense..
Sorry I don't understandCan i make 4 =DLookup in ONE texbox with 4 lines.
I want each lookup in seperate line.
Depends what you want to do. You might want to concatenate your address lines but separate them with vbCrLf. But that's for display, not storage or data entry.i reckon i dont use vbCrLf in a controll?