Design advice - Web based form submission
I have a brief for a solution in which:
- We have a contacts database ( this already exists and is referenced by 2 other of our files)
- Another file (new) will access contacts records ( and modify them as needed)
- Clients will need to submit a form requesting service (web based)
- We will approve the request (or not) and then promote the request to a new status (approved) at which point it becomes an active record in a table in the new file and we get to work organising.
- We will need to somehow link client forms (requests) to preexisting contacts (automated) or if they are a new client, to create a new one (this could be manual off the form information).
- Clients can not have access to any contact information that is not their own.
- Clients should have access to only their own web based form record.
So far I have thought of
- A separate file for request form records- referenced (related) to the New file and the contacts file
- Creating accounts via script in this separate file - linking (relating) client accounts to their own records and contact information scripturally using finds.
- Or just having plenty of criteria to relate a client's form to a contact record so their is low chance of error and then manually assigning the hitherto unrelated ones.
Any advise gratefully received.