newbie question on Form

  • Thread starter Thread starter Raymond Du
  • Start date Start date
R

Raymond Du

Hi,

I come from VB background, I use ADO a lot. I have a question, if I create
an ADP project and connect to SQL server, is it common to create forms using
unbound mode , which means not setting Record Source property. I reason I
want to do this is because I learned from VB this way is more scalable, yet
most of the forms sample I saw are bound to tables or views.

Thanks in Advance
 
Raymond Du said:
I come from VB background, I use ADO a lot. I have a question, if I create
an ADP project and connect to SQL server, is it common to create forms using
unbound mode , which means not setting Record Source property. I reason I
want to do this is because I learned from VB this way is more scalable, yet
most of the forms sample I saw are bound to tables or views.
Click to expand...

It's not binding the form that makes it scalable or not, but the size of the
recordset it's bound to. Binding to a table with a million records in it
will never be as scalable as binding to 1 record. The second consideration
is how long the session or lock will be maintained. If you allow your users
to get up and walk away from the form, you need a way to disable the lock. I
recently had a situation using unbound web forms where I had to increase the
session time from 10 minutes to 2 hours because the sales people were
allowed to walk away from a contract and come back to it later. This is not
a scalable solution, but it didn't need to be.

So to answer your question: Intelligently using bound forms will decrease
you development time significantly because to have far less code to write
(and maintain). But you can do it either way. I prefer using both, and only
experience will tell you when one or the other method is more appropriate.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access
 
Back
Top