ineuw (MIS) Aug 9, 2004 wrote:
Unbound forms give greater flexibility for the programmer and the user. In both cases, it's easier to evaluate the data before saving it. I can branch off to numerous public functions to evaluate and calculate prior to saving, without blocking other users' access to the record. With bound forms, I end up doing all data evaluation in the form's BeforeUpdate event and sometimes, that makes for a very long procedure to manage. Unbound also give much greater flexibility in form design and I use pop up forms everywhere except where the number of fields requires a full screen.
----------------------------------------------------
If it is difficult to manage BeforeUpdate event, what about Load and unload events with unbound forms? Also what is faster to load? bound or unbound form? What about going to the next or previous record? delete record? update record? Unbound forms require to code each step, how it impacts the database productivity?
Sometimes blocking is not bad feature, it is helping to manage user's access to the same data.
It will be interesting to know the opinion of different programmers about this question.
Thanks in advance to all responders!
Just remark: our company collected customers (software users) feedback about popup forms. Most of them (about 80%) don't like any pop ups and prefer to have all necessary information on the one screen, pop up warnings is ok.
Best Regards,
Iryna
Unbound forms give greater flexibility for the programmer and the user. In both cases, it's easier to evaluate the data before saving it. I can branch off to numerous public functions to evaluate and calculate prior to saving, without blocking other users' access to the record. With bound forms, I end up doing all data evaluation in the form's BeforeUpdate event and sometimes, that makes for a very long procedure to manage. Unbound also give much greater flexibility in form design and I use pop up forms everywhere except where the number of fields requires a full screen.
----------------------------------------------------
If it is difficult to manage BeforeUpdate event, what about Load and unload events with unbound forms? Also what is faster to load? bound or unbound form? What about going to the next or previous record? delete record? update record? Unbound forms require to code each step, how it impacts the database productivity?
Sometimes blocking is not bad feature, it is helping to manage user's access to the same data.
It will be interesting to know the opinion of different programmers about this question.
Thanks in advance to all responders!
Just remark: our company collected customers (software users) feedback about popup forms. Most of them (about 80%) don't like any pop ups and prefer to have all necessary information on the one screen, pop up warnings is ok.
Best Regards,
Iryna