Search results

You could make your application into an .MDE which compiles all code and makes the whole system inaccessible to changes. - Always make a backup first, because you will not be able to do any mods yourself to this file, Or you could implement full user level security and then set the permissions...

Add whatever field is the first field in the query that fills cboProjectName to the query that fills cboSub. In the criteria section of this field in (qrycboSub) add Forms!frmTheNameOfTheForm!cboProjectName. Then in AfterUpdate of cboPrjectName - (in the code) - add: Me!cboSub.Requery

In the Date field of the query that fills your new form, add the criteria: Between[Enter start date] And [Enter end date] This will force the user to input to dates which will limit the size of the recordset returned by the query

You have to give Access more information - Max of what???? it could be anything that appears on your form. Have a look in the help under DMax!

You can use the BeforeUpdate event to fire if a recordset has been changed, this will fire before the data is written to the tables and will only fire if the data has changed

The form property set to Data Entry - Yes will only allow you to input to a 'new' single form! If you take the Yes off you will need to use the AddNew to generate a new record. Data Entry set to YES is used when you want to open a form and enter new records only.