Hello,
Has anyone come across this problem.
I have a database where I use a single form (frmPatientDetails) both to Enter new patients and also to View the details for existing patients.
I use DoCmd.openform frmPatientDetails, , , , acFormAdd to open the form in data entry mode. When viewing exsting records I use simply DoCmd.openform frmPatientDetails
3 users use the database regularly (they each have their own copy). One of them has twice reported a problem that when trying to view patient details, the form opens with all fields blank. It turns out (when I get a chance to look at it) that the forms DataEntry property is set to Yes. I don't set this property anywhere in the code, and it is set to No in all other copies of the database.
My question is - can this behaviour be caused by opening the form using acFormAdd. When opening the form to view details, should I explicitly state acFormEdit, or is it good enough to assume default behaviour.
Thanks for any pointers,
StepOne
Has anyone come across this problem.
I have a database where I use a single form (frmPatientDetails) both to Enter new patients and also to View the details for existing patients.
I use DoCmd.openform frmPatientDetails, , , , acFormAdd to open the form in data entry mode. When viewing exsting records I use simply DoCmd.openform frmPatientDetails
3 users use the database regularly (they each have their own copy). One of them has twice reported a problem that when trying to view patient details, the form opens with all fields blank. It turns out (when I get a chance to look at it) that the forms DataEntry property is set to Yes. I don't set this property anywhere in the code, and it is set to No in all other copies of the database.
My question is - can this behaviour be caused by opening the form using acFormAdd. When opening the form to view details, should I explicitly state acFormEdit, or is it good enough to assume default behaviour.
Thanks for any pointers,
StepOne