Originally Posted by
Kat-ness
...There may be applicants with multiple applications and I want a refresh button on the form that will refresh the applicant contact info throughout other records if something is updated for an applicant...
You're not talking about 'refreshing' data here! Refreshing means having data changes on a given Record, that has been modified by one user, reflected in that Record as seen by all users!
Originally Posted by
June7
...Are you saving all the applicant info into every application record...
This is exactly what you're doing and this is a basic mistake, as it means that your database is not Normalized, and Normalization is a basic requirement of a Relational Database! You should have 2 Tables here:
Applicant Table
ApplicantID as Primary Key
ApplicantName
ApplicantAddress
ApplicantTelephoneNumber
..........etc.
Applications Table
ApplicationID as Primary Key
ApplicantID as Foreign Key
ApplicationDate
...........etc.
You'd then use a Main Form (based on the Applicant Table) and a Subform (based on the Application Table.) These Forms would be used in a Main Form/Subform configuration, and linked using the common ApplicantID Field.
This will help to Normalize your database, as is proper, and will only require that Applicant data be changed in one Record.
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007