RuralGuy
AWF VIP
- Local time
- Today, 08:46
- Joined
- Jul 2, 2005
- Messages
- 13,819
Hi Lars,
Have you looked at and studied the NorthWind example that comes with Access? It is absolutely loaded with examples of a veriety different methods to accomplish tasks.
As a starter, a properly designed database only contains information like names and addresses once. You would have an account number in the table that would be placed in any other table (like your Trouble Ticket table) as a foreign key and then a query could link the two tables through this FK making the name and address available as if it were in the TroubleTicket table.
Have you looked at and studied the NorthWind example that comes with Access? It is absolutely loaded with examples of a veriety different methods to accomplish tasks.
As a starter, a properly designed database only contains information like names and addresses once. You would have an account number in the table that would be placed in any other table (like your Trouble Ticket table) as a foreign key and then a query could link the two tables through this FK making the name and address available as if it were in the TroubleTicket table.
