Should forms be binded to the table/query?

[techcrium]

I heard it's bad design to have forms directly binded to a query because you have no data control.

Is it better to make forms unbounded and then have users fill it out, and use VBA to programatically validate the data and insert into the database?

 

[pbaldy]

I use bound forms most of the time. You have plenty of control over the data. Jason has some thoughts here:

http://www.baldyweb.com/BoundUnbound.htm

 

[gemma-the-husky]

personally, i would use bound forms as much as possible, unless and until you get a situation that is user to accoumplish with an unbound form.

it's far easier to use bound forms.

i am not sure about the last bit of advice in paul's link. I don't necessarily think that a non-Jet/Ace database makes unbound forms more advisable. If that were so, then upsizing a dbs would always require a complete rewrite.
.

 

[pbaldy]

I don't necessarily think that a non-Jet/Ace database makes unbound forms more advisable. If that were so, then upsizing a dbs would always require a complete rewrite.

I use bound forms against SQL Server back ends most of the time. I think Jason's point was that a non-Jet back end adds weight to the case for unbound, not that it requires it. It's still a matter of considering the factors for and against in a specific situation.