Setting a limit to number of entries of a form
Course Details Table / Form and Booking Details Table / Form.
They are both related.
I want to make it so that the Booking Form can only allow 30 entries of students per course.
The course details table has a course ID and other stuff for the course.
The booking form has a booking ID, course ID and student ID (I also have a students table).
Thank you for taking the time to report an issue.
What's wrong... Please write below.
Can I limit there read/write ability so that they can only add new entries and not accidentally delete things from the database.
Also, is there a way to make sure they don't enter duplicate data. I.e. Engineer 1 enters information for part number X, but tomorrow Engineer 2 goes to enter same part number X.
If they could see the database table, they could search and see if it had been entered already, but I don't want to give them access to the entire database. Ideally they would just beworking with a form and the form wouldn't allow them to enter duplicate entries in the part number field.
I have a table that allows for unlimited entries, but it needs to have at least 2 entries per Person (already connected relationally in a one-to-many). I need a calculated control for the form that can state how many more entries the Person needs by counting the number of entries that are already in the table.
For example, PersonA has 1 entry and the control would state that 1 more is needed. However, Person B has 3 entries and the control would simply be blank.
I plan to use the control in both a form and also a report.
What I would like to do is have a search form, in which the user enters the serial number, and a list appears for all of the entries with that serial number.
There will be multiple entries in each table for each project number. What I need to do is create a query (or series of) which will show me where for each project in table 4:
Where Actuals to Date (Table 2) + Future Forecast (Table 3) > Total Approved
Spend (Table 1)
And also which entry in the forecasting table causes the cumulative limit set in Table 1 to be breached and thus infer the date on which this will happen.
It's a bit more complicated than anything I've dealt with before so could
If they cancel the form will just be closed. If they save I want to save the entries into a different table, which will contain all the saved entries from each time the continuous form has entries that are saved. Each time the form is opened it needs to be empty.
I want to create a 'Purchase orders' Form. the form would look something like this:
Item number. Item description. Item quantity. other notes.
now, the purchase order could contain multiple entries(Items), but not specific to a certain number. like for example, in a single order you could place one item or two or five or ten. I could create a specific number of text boxes for the user to enter a certain amount of items, like seven or ten but this would be inefficient, non-practical and would clutter the form.
So, what would be the best practice of creating such a form?