cabusmichael
Registered User.
- Local time
- Today, 16:22
- Joined
- Aug 28, 2009
- Messages
- 17
Hello,
First off, thanks, everyone, for the responses I have had so far--they have been wonderful...
I am having a strange form-design problem.
I have a design in which grants fund specific projects. I have a relationship like this:
[contracts/grants] (N) ---- (1) [projects]
So, each contract/grant funds 1 project, and a project can be funded by more than 1 grant. I look at the relationships view, and the relationship is correctly mapping as a 1:N relationship.
I'm imagining the user going into the grant form, adding a new grant, and then adding the project name. Currently, I have the project name as a unique identifier, on the assumption that no two projects will have the same name.
When I create a form based on this table, a "project" field is present, but, if one tries to enter a new project name here, there is an error message "You cannot add or change a record because a related record is required in table 'Project'". I don't understand this--if the project field is present, why can't it write a new project name to the project table?
I have thought of one solution--adding a project subform that can be used for adding new project name (say "New Jersey Pine Barrens restoration project"); then, the user could enter in the project name in the in the Contract/Grants form. It works, but it is not very elegant..
Is there a better way to configure this?
Thanks for reading, and any helpful response--very much appreciated!
Michael
Thanks for any help,
Michael
First off, thanks, everyone, for the responses I have had so far--they have been wonderful...
I am having a strange form-design problem.
I have a design in which grants fund specific projects. I have a relationship like this:
[contracts/grants] (N) ---- (1) [projects]
So, each contract/grant funds 1 project, and a project can be funded by more than 1 grant. I look at the relationships view, and the relationship is correctly mapping as a 1:N relationship.
I'm imagining the user going into the grant form, adding a new grant, and then adding the project name. Currently, I have the project name as a unique identifier, on the assumption that no two projects will have the same name.
When I create a form based on this table, a "project" field is present, but, if one tries to enter a new project name here, there is an error message "You cannot add or change a record because a related record is required in table 'Project'". I don't understand this--if the project field is present, why can't it write a new project name to the project table?
I have thought of one solution--adding a project subform that can be used for adding new project name (say "New Jersey Pine Barrens restoration project"); then, the user could enter in the project name in the in the Contract/Grants form. It works, but it is not very elegant..
Is there a better way to configure this?
Thanks for reading, and any helpful response--very much appreciated!
Michael
Thanks for any help,
Michael