the situation essentially revolves around enabling a data entry clerk to decide whether or not to enter a record. let's think of two forms 'A' and 'B'.
table 'A' contains a field called 'IRB' which should not have more rows entered (associated with it) than are to be found specificed in a field call 'IRB Limit', and 'IRB Limit' appears in the other table we're calling 'B'. as the clerk enters a record, (s)he enters the information in the 'IRB' fields and what is wanted is an ability to test if that record exceeds the value found in the 'IRB Limit' field of table 'B'. if so, then the decision to abort the data entry for this 'IRB' is made. if not, the record is entered.
i currently think that this can't be done 'on the fly' so to speak and that it requires aggregating the number of records per 'IRB', comparing the count computed with the 'IRB Limit' value (say in a query) and messaging the result. is this necessarily true?
table 'A' contains a field called 'IRB' which should not have more rows entered (associated with it) than are to be found specificed in a field call 'IRB Limit', and 'IRB Limit' appears in the other table we're calling 'B'. as the clerk enters a record, (s)he enters the information in the 'IRB' fields and what is wanted is an ability to test if that record exceeds the value found in the 'IRB Limit' field of table 'B'. if so, then the decision to abort the data entry for this 'IRB' is made. if not, the record is entered.
i currently think that this can't be done 'on the fly' so to speak and that it requires aggregating the number of records per 'IRB', comparing the count computed with the 'IRB Limit' value (say in a query) and messaging the result. is this necessarily true?