tracking applications to a service

[daneharnett]

Hi,
Im building a system that tracks peoples applications to our service, a person can apply more than once and the application is made in various steps at certain steps the person can be 'rejected' or 'referred on' or they can proceed to the next step...

Certain data will be collected at each step, the steps are:
1. Initial Contact
2. Assessment
3. Admission

At Initial Contact if the person has not applied before then we will need thier personal details (name, address, phone etc) otherwise we will just collect the specific information about this application...
At Assessment we will gather more information about the application.
At Admission we will input information about thier acceptance into the program.

Now each Assessment will need to be linked to an Initial Contact... and an Admission will need to be linked to an Assessment...
This is the general table structure i have thought of:

tblClients
- ClientID
- Name, Address, Etc etc
tblInitialContacts
- InitialContactID
- ClientID
- Other info
tblAssessments
- InitialContactID
- other stuff
tblAdmissions
- InitialContactID
- other stuff


What do u think of this structure and general problem?

 

[lebisol]

sounds good to me....keep the ClientID related through out the tables.
take a look at the structure of the DB at

http://tdsf.co.uk/tdsfdemo/Tutorial04.htm

perhpas it will give u more ideas on how to structure your project
also the Mr. Grim R.

http://support.microsoft.com/?kbid=209534

> need more info?
:: don't click HERE ::