- Local time
- Today, 14:48
- Joined
- Feb 19, 2002
- Messages
- 47,202
If your query is not updateble, your form is not updateable. So, nothing is required to "guard" it. Since the OP's query aggregates data, it is not updateable.Oh yeah, but your form's bound, so you gotta disable stuff here, add guards there, fix this, fix that. Not exactly a high IQ move for a simple read-only feature. Honestly, it's like bringing a tank to a pillow fight. You don't need all that. Believe me.
Of course not but why?I do not think Pat would have any argument about a read only unbound form in single form view (maybe I am wrong).
Once you need CRUD or even the ability to scroll, you should just make a bound form. There is nothing inherently better about an unbound form. You will know based on your work with an app to date, whether you have to even consider unbound forms. You will more likely need to use an unbound form if you are connecting over the internet to your BE. Since very few applications actually do that, there are very few applications where you would even consider the possibility of starting with an unbound form unless you're getting paid by the hour and your client is clueless.
There are certain business scenarios where you have to enter all the child records before you commit a parent. Some people choose to use unbound forms in that case. But there are other, simpler solutions such as shadow tables that are used to create and validate the set of data before committing to the production table.
For the case in the original question, there is simply no reason to even consider using an unbound form although the amount of extra work to do so for a single record, noupdatable form is negligible.
The OP will be far better served by learning how the form's event model works so he can use the features of the RAD tool to control how bound forms and reports work. Here some videos and a sample database to work with to help you learn how the form's event model works. Use the existing forms or create your own and add them to the sample. Use the sample to investigate control events also. You can even add reports. Just follow the pattern and use the one line of logging code in any event you want to follow.
Bad Data is Bad for Business #1 and #2
I just added #2 --- that link is further down. It is much shorter than #1. I also added a copy of the database I used for the video. Enjoy:) I created a database to help people to understand how and why to use the Form's BeforeUpdate event to validate data. @Uncle Gizmo and I made a...
www.access-programmers.co.uk