bound vs unbound

[iccsi]

I learn that unbound form has better performance and have an unbound
application.

I just realized that I need write SQL for insert, update, delete and
search SQL for every unbound form.
When it comes any changes of function or database structures then I
have to modify SQL every where in the application.


I am not sure I am on the right track. If I am not can you please give
me some advise about this?
Are there any way to find the best way to choose bound or unbound form
applications?


Your information is great appreciated,

 

[Roger Carlson]

That an unbound application has better performance is an opinion, not a
fact. It's truth depends upon a lot of variables. Sometimes an unbound
application is faster, but often there is no perceptible difference to the
user. If your application is running within specifications for Access, that
is, the database isn't too large and you don't have too many concurrent
users, most of the time, bound forms work just as well. And in fact, they
are much easier to create and modify.

Just my opinion, of course.

--
--Roger Carlson
MS Access MVP
Access Database Samples: www.rogersaccesslibrary.com
Want answers to your Access questions in your Email?
Free subscription:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=ACCESS-L

 

[John W. Vinson]

I learn that unbound form has better performance and have an unbound
application.

I just realized that I need write SQL for insert, update, delete and
search SQL for every unbound form.
When it comes any changes of function or database structures then I
have to modify SQL every where in the application.


I am not sure I am on the right track. If I am not can you please give
me some advise about this?
Are there any way to find the best way to choose bound or unbound form
applications?


Your information is great appreciated,

I'd agree with Roger. Use bound forms for starters; if you have DEMONSTRATED
performance problems and have done all the reasonable things to fix that
(split application, resolved networking issues, proper indexing, etc. etc.)
then fall back to the much more laborious unbound forms.

But don't assume that bound forms always have inadequate performance. They
don't.

See
http://www.granite.ab.ca/access/performancefaq.htm for suggestions to tune up
Access performance.