I can answer almost all types of questions relating to Microsoft Access usage and application design. My strengths are database and interface design.
I've been designing databases for over 25 years working with dBase, FoxPro, Approach and Access.
Author of Microsoft Office Access 2007 VBA
Techncial Editor for Special Edition Using Microsoft Access 2007 and Access 2007 Forms, Reports & Queries From Que Publishing
Brooklyn College BA
|Oleg||02/12/17||10||10||10||I agree but the situation is even .....|
|Oleg||02/02/17||10||10||10||Thank you very much!|
|Oleg||01/27/17||10||10||10||Thank you very much.|
|OB||01/20/17||10||10||10||Thanks a lot.|
Ok, Are you sure that is form? Try it like this: Forms!formname!controlname = Nz(DMax(“[Claim Reference]”,”tblWarrantyClaims”),0)+1 Use the actual form and control names. it is not a good
Read my blog on Securing the Back End But frankly, if you have people who will try to get past the front end, then you have a bigger problem. I have well over 100 Access apps and I don't use extraordinary
I would do it differently. DoCmd.OpenForm "frmTimEntry",,,,acAdd Then, on frmTimeentry I would set the default value for txtValue2 to Forms!frmLogin.txtValue1. The problem is likely that the
You can open the form in Add Mode and then assign values to the controls. Or you could set the default value to read from the referenced control.
Don't use .Value. first it its the default value when referencing a control on a form and that's not what you are doing. You are referencing a variable passed to the procedure. You should be using:
Answers by Expert: