Tina, this is the culprit! I'm using this code to keep the user in
the
new record (condition "1"), and forcing use of (Undo/Save/Quit)
buttons.



Private Sub Form_BeforeUpdate(Cancel As Integer)
'stay on new record until save or quit
If (Me.OpenArgs = "1") And (Not (blnDone)) Then
Cancel = True
End If
If (Me.OpenArgs = "3") And (Me.Dirty) Then
If Not blnDone Then
MsgBox "Please (Undo) (Save) or (Quit)", vbExclamation,
"Not Complete"
Cancel = True
End If
End If
End Sub

comments inline.

<codepug (AT) gmail (DOT) com> wrote

well, scrolling the subform records requires that you *enter* the subform,
and you can't enter the subform until the record saves to the table.

first of all, you're modifying data in the *table*, and your subform is
bound to that table. but that's really beside the point. subforms are a GUI
feature of Access that were designed for a specific purpose: to make it
easy to add/edit records in a parent table, and then add/edit related
records in a related child table. and in that context, the fact that a
parent record is *automatically* saved before the subform receives the
focus, makes perfect sense and is a valuable safeguard helping to ensure
relational integrity. the fact that subforms can be utilized for
unconventional situations is a side benefit of the flexibility of Access -
but as developers we can't expect optimal performance in these situations.

here's where you're making a common mistake. a form is a form. it behaves as
a subform when it is set as the SourceObject of a subform control within
another form. if you open a form as a popup, it's just a form - it's not a
subform object and there's absolutely no reason to expect it to be governed
by any of the behaviors that are specific to subform objects within mainform
objects.

you're very welcome.

yes, very handy, that. if you read up on the
LinkChildFields/LinkMasterFields properties in Help, you'll find that you
can actually set the LinkMasterFields property to a textbox, a combobox,
even to an expression - anything that returns a valid key value, with the
proper DataType, that will match key values in the subform's RecordSource.
you can actually set the LinkChildFields property to an expression, *but not
directly*; instead, you have to use a query as the subform's RecordSource,
and include the expression as a calculated field in the query.

there you go. you'll have to decide which is more important to your process
flow - that only complete records be written to the table, or that the user
be able to review multiple subform records in the middle of entering a new
record. if both are important, then it might be a better option for your
users to provide them with a pop-up form instead of a subform, to display
historical attendance records. or use a listbox (you didn't answer my
earlier question in this thread, regarding what problems you encountered in
using a query with calculated fields as the RowSource of a listbox control).

hth


<codepug (AT) gmail (DOT) com> wrote

Tina

Thank you for the incredible tips and insight. I enjoyed every minute
of it!
I should probably spend more time in the books firming up the
fundamentals, but
I more frequently find myself freelancing and blindly exploring and
experimenting to my hearts content.

I’m working another aspect of my project now, and have discovered that
calculated fields and conditional formatting can quickly overburden a
continuous form, and result in screen flashing, and looping struggles.
So, I discovered that an SQL Query can substitute and eliminate some
of these problems. Now I struggle with attempting to reference a
textbox in the row with my SQL query (not doing well with that), and
additional problems with getting a user defined function that performs
many calculations based on public variables to somehow fit in, and I’m
not doing to well with that either.

It’s probably time for the book.

Thanks Again
Greg

you're very welcome, Greg. i enjoyed it too - subforms are near and dear to
my heart because they're so useful and so handy, and i work with them quite
a lot in my user interfaces. but i don't often see threads discussing
non-standard subform setups, so it was fun to dig into it. good luck with
your project!


<codepug (AT) gmail (DOT) com> wrote

Tina

Thank you for the incredible tips and insight. I enjoyed every minute
of it!
I should probably spend more time in the books firming up the
fundamentals, but
I more frequently find myself freelancing and blindly exploring and
experimenting to my hearts content.

fields as the RowSource of a listbox control).

I’m working another aspect of my project now, and have discovered that
calculated fields and conditional formatting can quickly overburden a
continuous form, and result in screen flashing, and looping struggles.
So, I discovered that an SQL Query can substitute and eliminate some
of these problems. Now I struggle with attempting to reference a
textbox in the row with my SQL query (not doing well with that), and
additional problems with getting a user defined function that performs
many calculations based on public variables to somehow fit in, and I’m
not doing to well with that either.

It’s probably time for the book.

Thanks Again
Greg