Hi all:
New Access user and new member here. I'm not entirely sure my issue is with forms, but thought I'd start here. I am trying to create a database that tracks applications to a program. On the surface, it seems fairly simple. An application is received and contains a host of basic identifying information. Each applicant has a unique nine digit identification number. I need to track the status of these applications and my issue involves multiple applications for a single person. That is, one individual can submit multiple applications across time. For example, John (ID 999999999) submits an application on 2010.01.01 and it is not accepted. He then re-applies five years later 2015.01.01 and is accepted.
For some reason, I can't create a relationship and form which allows for me to track multiple applications from a single person. Again, this seems fairly simple on the surface. The unique 9 digit user ID could be my "anchor" and then attached to multiple applications. I have tried creating two tables - one with basic identifying info (name, age, DOB, etc) and another table that contains application information (date app submitted, status of outcome, etc). I'm at a loss. Any help would be greatly appreciated. Thanks.
New Access user and new member here. I'm not entirely sure my issue is with forms, but thought I'd start here. I am trying to create a database that tracks applications to a program. On the surface, it seems fairly simple. An application is received and contains a host of basic identifying information. Each applicant has a unique nine digit identification number. I need to track the status of these applications and my issue involves multiple applications for a single person. That is, one individual can submit multiple applications across time. For example, John (ID 999999999) submits an application on 2010.01.01 and it is not accepted. He then re-applies five years later 2015.01.01 and is accepted.
For some reason, I can't create a relationship and form which allows for me to track multiple applications from a single person. Again, this seems fairly simple on the surface. The unique 9 digit user ID could be my "anchor" and then attached to multiple applications. I have tried creating two tables - one with basic identifying info (name, age, DOB, etc) and another table that contains application information (date app submitted, status of outcome, etc). I'm at a loss. Any help would be greatly appreciated. Thanks.