Confused about docmd.openform

[Thelma Lubkin]

formA determines some_where and some_value and issues

docmd.close ,Me
docmd.openform "formB", , ,some_where, , ,some_value

formB receives the correct some_where and some_value
After completing its work formB issues

docmd.close ,Me
docmd.openform "formA"

formA determines a new some_where and some_value and again issues

docmd.close ,Me
docmd.openform "formB", , ,some_where, , ,some_value

formB receives the correct some_where but no update of some_value

I also note that the forms' OnOpen event-code executes only the first
time that the forms are opened. How do I pass a new OpenArgs value to
formB after the first time?

I'm suspicious about where I've placed the close statements, but
neither order makes sense to me: if I close the form first, how does
the closed form execute the open statement that comes after the close
statement? ...but if I open the next form first, haven't I left the
environment where the close statement exists? And if my open
statements are failing, then why is *part* of the open statement
executing correctly [the some_where]?

--thelma
rephrasing an unanswered question

[Thelma Lubkin]

Larry Linson <bo*****@localh ost.not> wrote:
: "Thelma Lubkin" wrote

: > Public AgcID, EmpKey As Long
: > Dim AgcCol, PCnt As Integer
: > Dim GString As String

: Thelma, unless you are aware that AgcID and AgcCol are defined here as
: Variants, you could be in for some surprises sometime.

Thank you. I, indeed, didn't know that. Can you recommend a
book for someone who prefers code to wizards but who isn't
so dedicated as to want to write the class for each button
from scratch. The few books I've seen seem to assume one or the
other of the two extreme positions.
--thelma
: Larry Linson
: Microsoft Access MVP

[Larry Linson]

The book that almost every experienced Access developer of my acquaintance
has and swears by (not at) is the "Access Developer's Handbook" by Litwin,
Getz, et al. There's an edition for every version of Access _except_ V 1
(developer stuff was kinda primitive) and 2003 (not much change from 2002).

Getz et al have also done a book just on VBA, but it is not particularly
Access-oriented. I didn't find it very useful, as I do little or no VBA for
Excel, Word, etc.

I used to recommend Dr. Rick Dobson's, "Programmin g Access <version>" for
people moving from power user to developer, but now I suggest you browse it,
too. It strongly emphasizes ADO, which knowledgeable Microsoft insiders no
longer recommend, and the Access ADP client to SQL Server. He writes well,
and is a good teacher, but the subjects may not be what you are looking for.
The Access 2000 version may be more useful than later ones.

Another book I like is "Access 2003 Inside Out" by John Viescas, from
Microsoft Press. Better browse it at your local bookstore, though, to see if
it has enough VBA.

There are book recommendations at the FAQ, http://www.mvps.org/access, too,
from knowledgeable Access folks.

Larry Linson
Microsoft Access MVP
"Thelma Lubkin" <th****@alpha2. csd.uwm.edu> wrote in message
news:da******** **@uwm.edu...

Larry Linson <bo*****@localh ost.not> wrote:
: "Thelma Lubkin" wrote

: > Public AgcID, EmpKey As Long
: > Dim AgcCol, PCnt As Integer
: > Dim GString As String

: Thelma, unless you are aware that AgcID and AgcCol are defined here as
: Variants, you could be in for some surprises sometime.

Thank you. I, indeed, didn't know that. Can you recommend a
book for someone who prefers code to wizards but who isn't
so dedicated as to want to write the class for each button
from scratch. The few books I've seen seem to assume one or the
other of the two extreme positions.
--thelma
: Larry Linson
: Microsoft Access MVP

[Thelma Lubkin]

Larry Linson <bo*****@localh ost.not> wrote:
: The book that almost every experienced Access developer of my acquaintance
: has and swears by (not at) is the "Access Developer's Handbook" by Litwin,
: Getz, et al. There's an edition for every version of Access _except_ V 1
: (developer stuff was kinda primitive) and 2003 (not much change from 2002).

: Getz et al have also done a book just on VBA, but it is not particularly
: Access-oriented. I didn't find it very useful, as I do little or no VBA for
: Excel, Word, etc.

: I used to recommend Dr. Rick Dobson's, "Programmin g Access <version>" for
: people moving from power user to developer, but now I suggest you browse it,
: too. It strongly emphasizes ADO, which knowledgeable Microsoft insiders no
: longer recommend, and the Access ADP client to SQL Server. He writes well,
: and is a good teacher, but the subjects may not be what you are looking for.
: The Access 2000 version may be more useful than later ones.

: Another book I like is "Access 2003 Inside Out" by John Viescas, from
: Microsoft Press. Better browse it at your local bookstore, though, to see if
: it has enough VBA.

: There are book recommendations at the FAQ, http://www.mvps.org/access, too,
: from knowledgeable Access folks.

Thank you. I'll look for these.
--thelma

: Larry Linson
: Microsoft Access MVP

[Thelma Lubkin]

rkc <rk*@rochester. yabba.dabba.do. rr.bomb> wrote:
: Thelma Lubkin wrote:

: <snip all>

: I do not see any reason to do battle with the simple way that
: Access provides to do what you want to do.

: Open the Agency form to a specific agency using:

: strfilter = "agencyid = " & AgcID
: DoCmd.OpenForm DoCmd.OpenForm "agency0toD ", _
: acNormal, , strFilter, _
: acFormReadOnly, acWindowNormal, _
: empID
: DoCmd.Close , "frmChooseAgenc y"

: In that order.
: Call that from the combo box OnClick event.

: Return to frmChooseAgency from the agency form using:

: DoCmd.OpenForm "frmChooseAgenc y"
: DoCmd.Close acForm, Me.Name

: Check for a valid empId in openArgs in the agency form's
: OnLoad Event. If one is found do your subform navigation
: by calling a sub routine defined in the subform's code
: module.
Thanks very much to all of you who helped me to write my
first vba form [ie my first experience of the environment
altogether] Thank you:

Arno R, Bas Coste Budde, dreadnought, Larry Linson, rkc,
Tom Stiphout, Wayne Morgan. I'm sorry if I've forgotten anyone.

It works about the way I want it to now. My major stumbling
blocks were using a toggle where I needed only a simple command
button, and misunderstandin g bookmarks so that I was trying to set a
parent-form's bookmark to that of its child.

--thelma

[Tony]

In a previous message you state:

I used to recommend Dr. Rick Dobson's, "Programmin g Access <version>" for
people moving from power user to developer, but now I suggest you browse
it,
too. It strongly emphasizes ADO, which knowledgeable Microsoft insiders no
longer recommend, and the Access ADP client to SQL Server. He writes well,
and is a good teacher, but the subjects may not be what you are looking
for.
The Access 2000 version may be more useful than later ones.

Can you expand on your statement about ADO and what is currently
recommended.
I am working through Dr. Dobson's "Programmin g Access 2003...".

Thanks

[Tony]

In a previous message you state:

I used to recommend Dr. Rick Dobson's, "Programmin g Access <version>" for
people moving from power user to developer, but now I suggest you browse
it,
too. It strongly emphasizes ADO, which knowledgeable Microsoft insiders no
longer recommend, and the Access ADP client to SQL Server. He writes well,
and is a good teacher, but the subjects may not be what you are looking
for.
The Access 2000 version may be more useful than later ones.

Can you expand on your statement about ADO and what is currently
recommended.
I am working through Dr. Dobson's "Programmin g Access 2003...".

Thanks