By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,773 Members | 2,583 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,773 IT Pros & Developers. It's quick & easy.

VBA or qry

P: n/a
When using forms are you best to use SQL or run VB code to load the
data from tables. Or is it just personal preference.

Anyone that can shed any light on this, would be appreciated.

TIA
Stephen
Nov 13 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
I don't understand the question.

Bound forms will use a table, a query, or an SQL statement as their
RecordSource. Under some conditions, it is possible to open a recordset to
use as the RecordSource, but, in my experience, it is always just as easy to
use the table, query, or SQL directly as RecordSource that you'd use to open
the Recordset. The exception _may_ be the use of "disconnected recordsets"
in an Access "project" (ADP/ADE).

To use unbound forms, you have to write VBA code to re-implement
functionality that Access provides with bound forms. Once I learned how
Access works, I only use unbound forms for Switchboards, Splash Screens, and
to allow users to select the records to be displayed or printed on another
Form or in a Report.

If that doesn't answer your question, please clarify.

Larry Linson
Microsoft Access MVP
"Steph" <st******@hotmail.com> wrote in message
news:a0**************************@posting.google.c om...
When using forms are you best to use SQL or run VB code to load the
data from tables. Or is it just personal preference.

Anyone that can shed any light on this, would be appreciated.

TIA
Stephen

Nov 13 '05 #2

P: n/a
The whole point of using Access rather than developing from scratch in VB or
C is to take advantage of its rapid development environment. That includes
bound forms, which provide a great set of events for validating and
manipulating the fields and the record, and the subform which displays
related records so easily.

In most cases where Access is a suitable tool, there is nothing to be gained
by wasting the effort to reinvent the wheel yourself. Get to know the few
events you really need such as BeforeUpdate, and put the to use.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Steph" <st******@hotmail.com> wrote in message
news:a0**************************@posting.google.c om...
When using forms are you best to use SQL or run VB code to load the
data from tables. Or is it just personal preference.

Anyone that can shed any light on this, would be appreciated.

TIA
Stephen

Nov 13 '05 #3

P: n/a
On Tue, 10 Aug 2004 03:06:46 GMT, "Larry Linson"
<bo*****@localhost.not> wrote:
... Once I learned how Access works ....


Ah, the good old days! I'm still trying

Nov 13 '05 #4

P: n/a

"David Schofield" <d.***************@blueyonder.co.uk> wrote in message
news:4118e700.1893182@localhost...
On Tue, 10 Aug 2004 03:06:46 GMT, "Larry Linson"
<bo*****@localhost.not> wrote:
... Once I learned how Access works ....


Ah, the good old days! I'm still trying


I wouldn't put a lot of faith in Larry's statement.
Nov 13 '05 #5

P: n/a
"XMVP" <ac***********@hotmail.com> wrote
I wouldn't put a lot of faith in Larry's statement.


With what statement, in particular, do you disagree, Don?

Nov 13 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.