Form design for CRUD

[MDB]

Hi,



I am new to access but looking at the sample databases, the example forms don't have a submit (or ok) button to commit record changes. The data is updated straight after leaving a field in a form. Is this standard practise for commercial apps written in access?

Would the alternative optin be to include unbound text fields in a form and onclick of a sbmitt button perform crud operations programmatically using VBA?

Many thanks.
MDB

[Bob Fitz]

Hi

I am new to access but looking at the sample databases, the example forms don't have a submit (or ok) button to commit record changes. The data is updated straight after leaving a field in a form. Is this standard practise for commercial apps written in access?

That's what I do. You may want to write a little code to check data validation in the BeforeUpdate events of some controls or the actual form.

Would the alternative optin be to include unbound text fields in a form and onclick of a sbmitt button perform crud operations programmatically using VBA?

I would not normally do this because it needs a lot more code but it is possilbe to use an unbound form. I have taken this approach to speed thinks up when the app is split and used by multiple users on a busy network and the data is large.

[pbaldy]

I agree with Bob. I normally use bound forms, as you're letting Access do most of the work for you. I sometimes use unbound forms, most commonly when I have an app that needs to work via WAN instead of LAN.