which record navigation methods

[BBC via AccessMonster.com]

I currently use the standard DoCmd ... to navigate, create new and find the
records to display on my forms. Such as
DoCmd.GoToRecord , "", acLast or
DoCmd.RunCommand acCmdSaveRecord
etc.

Should I be using DAO (recordsets) to do this instead of the above. If so,
what are the benefits.
Any special things I need to do to have the form display the records and do I
need to set the current DB in each navigation function or is set by default
to the current form/bound table (or can it passed to the SUB as an argument
to make the SUB work the currently active form/boundtable).
Thnanks for any guidance

 

[Jack Leach]

Hi Brian,

I think you should continue using your current DoCmd methods to navigate and
drop any notion of switching to recordset to do this.

Access is built with native behind-the scenes handling for records in forms,
and doing this "manual" with recordsets seriously works against it's natural
flow. You can try if you like, but you will find that you will basically
have to re-write every aspect of how access forms work. It may be possible,
but not probable, and certainly not efficient.

DoCmd methods are provided so that we may let access do what it does best
and still have ample control over the navigation and data without having to
wrestle it from Access.

hth
--
Jack Leach
www.tristatemachine.com

"I haven't failed, I've found ten thousand ways that don't work."
-Thomas Edison (1847-1931)

 

[BBC via AccessMonster.com]

Thanks, appreciate the feedback. I was not wanting to change my current
record processing methods but saw some code that did it with recordsets,
looked more complicated andwas wondering what the advantage was.
I have been wanting to have one set of record navigation routines (subs) for
all forms in a single application (in a module ??) which I'm not sure how to
do using DoCmd (how does it know which form/table is active or does it simply
use the current db/table/form, or can it be passed that info).
The recordset code I looked at allowed for one set of routines for the entire
project (all forms/tables within it)
thanks again

Hi Brian,

I think you should continue using your current DoCmd methods to navigate and
drop any notion of switching to recordset to do this.

Access is built with native behind-the scenes handling for records in forms,
and doing this "manual" with recordsets seriously works against it's natural
flow. You can try if you like, but you will find that you will basically
have to re-write every aspect of how access forms work. It may be possible,
but not probable, and certainly not efficient.

DoCmd methods are provided so that we may let access do what it does best
and still have ample control over the navigation and data without having to
wrestle it from Access.

hth

I currently use the standard DoCmd ... to navigate, create new and find the
records to display on my forms. Such as

[quoted text clipped - 9 lines]

to make the SUB work the currently active form/boundtable).
Thnanks for any guidance