unbound forms

[icccapital]

I have a form that has a recordsource based on a query I typed in and I have
all the controls on the form unbound. I believe with a bound control it
keeps a link to the database so there is a lot of communication between form
and database right? With an unbound form does the recordsource "download" a
recordset that the form then walks through? So if I add a next button to the
form, when next is clicked does the form requery the database or does it get
the data from the recordset?

I am working in access 2007 and right now the database is split with the
backend still in access, but I hope to move it to sql server so that is part
of the reason I am trying to unbind some of the information, to improve
performance after the move.

Thanks for the thoughts.

 

[golfinray]

Unbound forms are not less complex, but MORE. Having to set recordsources on
the fly is something you should avoid. Bind the forms to a table or query
then when you upgrade the sql it will be easy to set the links. Google unc
paths to find out how.

 

[David W. Fenton]

Unbound forms are not less complex, but MORE.

Very true -- you have to put in a whole bunch of code to replicate
features and events that you get without code in a bound form.

Having to set recordsources on
the fly is something you should avoid.

Why? I see absolutely no reason to avoid it. Indeed, I'd say it's
the first choice for any form.

Bind the forms to a table or query

Terrible idea -- it may work with small tables, but quickly becomes
inefficient. It's also very bad if you try to upsize it.

then when you upgrade the sql it will be easy to set the links.
Google unc paths to find out how.

UNC has zilch to do with the subject of bound/unbound.

 

[icccapital]

golf, linq, bruce and david--

Thank you all, this is a great discussion. I am fairly new to front end
design and using all the tools out there to create them. I have for classes
done some database frontend with php and because I found it unweildy for
creating gui I decided to create it in Access. But please, let me know what
your favorite (best) way to create a frontend gui that you have found, I am
very interested to learn.

Also, as stated before I have found the limitations of the jet database
engine too much and would like to move to a sql express backend, so much of
what I am doing now is to help with that transfer. When I did a first test
upscale to sql and ran it, I found it to be terribly slow because it turned
out that access forms were making a lot of calls to the database so I was
attempting to simplify that part of it. Please let me know your thoughts on
what the best way to goa bout this is, assuming I don't switch to another
frontend.

I know this might be vague so ask directing questions. I hate to make the
question so long by adding every detail I know.

Thanks again for all the thoughts and help.