OK, The government will not permit a ham to belong to more than one MARS group at a time. Therefore if you are a MARS operator you either have to be Air Force, Army, or Navy. You do not have to be in the military now or ever. I think they eliminated Navy, but just incase there are some Navy operators in the club it's best to keep the field.MARS either/or problem
I will need an explanation of this problem.
I think there's a table called tblMars set the index in there.
I think there's a field rosterID and marsdesc, set the index to unique on these two fields.
All the reports and forms work fine in my version.
Set the forms data entry property to no.
I meant the subform.
Have you added Marsindex?
The example db you provided has two records.
However I gather from your comments that this is an existing concern.
That leads me to ask, how are you going to add the records from your existing system to the new system!
I suggest you do some experiments and see if you can copy the data into the new database. Not much point in continuing until this issue is resolved.
The only thing I copied was the data from the old Roster table. I did not copy the structures or anything else. I renamed the old fields so the copy and paste would accept them. I pasted that into the tblRoster table.
I'll do that again to be sure.
Well, if it's essentially the working copy I posted earlier, then I'd like to see why its not working now.
I note that the affiliate table, and one or possibly two of the other tables have some blank cells in them. You need to add indexes to prevent null values being added to the table.
You can prevent deletion like that by going to the forms properties and setting allow delete to "no".
You might want to consider doing that in most places in your database because it is not considered good policy to allow your database user to delete records willy-nilly as this can cause you all sorts of problems.
When offering the user the option to delete records, I actually don't allow them to delete the record. I put a flag in the record, basically a check box which when checked indicates the record has been deleted. This is a good tip and can save you a lot of heartache.
You can then write a routine for removing deleted records safely under the control of someone who knows what they are doing, the database administrator for instance.
Talking about deleting records reminded me of relationships. I'm pleased to note you haven't got any relationships setup yet, to my mind they are a hindrance to the initial stages of database development. Once you are happy with the structure of your database then you might want to consider adding relationships. I suggest you read up on them first, and then add them to a temporary copy of your database to see what happens, before adding them to your main database.