Unbound Nested Subform Simulating Continuous Form

[Robert]

Need some help to stop me going around in circles on this one....

Have a nested subform (subform2) which simulates a continuous form for the
record on the parent subform.

Subform2 has rows of either an option button plus two text fields or a
checkbox plus two text fields

Am wanting to save the user entries into an underlying table. Tag property
for each option button, check box or text field has the value of the key
field for each record to be saved to the underlying table.

Any help/suggestions on best way to do this appreciated.

Thanks

Bob

[Allen Browne]

Why use an unbound form, when you want to save the values into a table?

Why go to the trouble of trying to simlate an unbound continuous form when a
bound one is handed to you on a platter and requires next to effort to
develop?

The "best way" will be to use a bound continuous subform.

--
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.

"Robert" <ro*******@bigp ond.com> wrote in message
news:vj******** ***********@new s-server.bigpond. net.au...

Need some help to stop me going around in circles on this one....

Have a nested subform (subform2) which simulates a continuous form for the
record on the parent subform.

Subform2 has rows of either an option button plus two text fields or a
checkbox plus two text fields

Am wanting to save the user entries into an underlying table. Tag property
for each option button, check box or text field has the value of the key
field for each record to be saved to the underlying table.

Any help/suggestions on best way to do this appreciated.

Thanks

Bob

[Robert]

Allen,

Started with a bound subform but switched to using an unbound subform for
better error control, more control over saving records (single button on
parent subform) and for more user friendly data capture (option buttons &
check boxes rather than combo boxes on continuous subform).

Parent subform has "Project" (one) details and nested subform has (many)
"Products" that can be selected via option buttons or check boxes and layout
of the form is not on a one record (Product) per row basis.

"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:43******** **************@ per-qv1-newsreader-01.iinet.net.au ...

Why use an unbound form, when you want to save the values into a table?

Why go to the trouble of trying to simlate an unbound continuous form when
a bound one is handed to you on a platter and requires next to effort to
develop?

The "best way" will be to use a bound continuous subform.

--
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.

"Robert" <ro*******@bigp ond.com> wrote in message
news:vj******** ***********@new s-server.bigpond. net.au...

Need some help to stop me going around in circles on this one....

Have a nested subform (subform2) which simulates a continuous form for
the record on the parent subform.

Subform2 has rows of either an option button plus two text fields or a
checkbox plus two text fields

Am wanting to save the user entries into an underlying table. Tag
property for each option button, check box or text field has the value of
the key field for each record to be saved to the underlying table.

Any help/suggestions on best way to do this appreciated.

Thanks

Bob

[Lyle Fairfield]

What's your question?
You want to save some values?
And you don't want to do it the Access way?

You, of course, are way better than those stiffs who designed Access on
the one hand, but on the other hand, you don't know how to solve this
simple problem? Fabulous! Congratulations !

So save them. Use an INSERT INTO query if they're new. Use an UPDATE
query if they're not.
What's the problem?

[Allen Browne]

If you do come up with a better design that the one Access gives you for
free, please let us know.

--
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.

"Robert" <ro*******@bigp ond.com> wrote in message
news:1S******** ************@ne ws-server.bigpond. net.au...

Allen,

Started with a bound subform but switched to using an unbound subform for
better error control, more control over saving records (single button on
parent subform) and for more user friendly data capture (option buttons &
check boxes rather than combo boxes on continuous subform).

Parent subform has "Project" (one) details and nested subform has (many)
"Products" that can be selected via option buttons or check boxes and
layout of the form is not on a one record (Product) per row basis.

"Allen Browne" <Al*********@Se eSig.Invalid> wrote in message
news:43******** **************@ per-qv1-newsreader-01.iinet.net.au ...

Why use an unbound form, when you want to save the values into a table?

Why go to the trouble of trying to simlate an unbound continuous form
when a bound one is handed to you on a platter and requires next to
effort to develop?

The "best way" will be to use a bound continuous subform.
"Robert" <ro*******@bigp ond.com> wrote in message
news:vj******** ***********@new s-server.bigpond. net.au...

Need some help to stop me going around in circles on this one....

Have a nested subform (subform2) which simulates a continuous form for
the record on the parent subform.

Subform2 has rows of either an option button plus two text fields or a
checkbox plus two text fields

Am wanting to save the user entries into an underlying table. Tag
property for each option button, check box or text field has the value
of the key field for each record to be saved to the underlying table.

Any help/suggestions on best way to do this appreciated.

[Robert]

Lyle,

Sorry new at access, am using a currentdb.execu te "insert into...statemen t
for new records being added. Have product number (unique identifier) in the
tag property of each control which allows grouping controls into records.
Just not sure on how to read through all the controls of the nested subform
and group them into records using the tag property including for each record
specifyig which control is to be saved to which feld before using the insert
into query.

"Lyle Fairfield" <ly***********@ aim.com> wrote in message
news:11******** **************@ o13g2000cwo.goo glegroups.com.. .

What's your question?
You want to save some values?
And you don't want to do it the Access way?

You, of course, are way better than those stiffs who designed Access on
the one hand, but on the other hand, you don't know how to solve this
simple problem? Fabulous! Congratulations !

So save them. Use an INSERT INTO query if they're new. Use an UPDATE
query if they're not.
What's the problem?

[Lyle Fairfield]

Probably how to read through would depend on how you created them in
the first place. You say your nested subform simulates a continuous
form? How? Is the initial data (that is displayed) part of a recordset?
Where does it come from? How many rows are on this simulated continous
form? How is this number decided? What happens when the user wants to
create a new row? What happens when the user wants to delete a row? If
you use recordset is it a DAO or ADO recordset? etc. etc etc.

[Robert]

Lyle,

Nested subform appears to user as as a single form containing a number of
option buttons (4), a number of text boxes (12) and check boxes (11).

Each pair of the option buttons (not option group) represents an either/or
product choice

Each check box represents a product choice.

The text boxes are some additional fields used for additional info that
relate to 6 of the product choices (option buttons/checkboxes)

Subform is being used for initial data entry (same methodology will be used
to edit existing records but via a separate view/edit form). During initial
data entry user can include/exclude products by selecting/unselecting the
optionbuttons/checkboxes.

User enters details for a single project on the parent subform and selects
one or more products (multiple) on the nested subform.

Am using ADO to add record on the ubound parent subform and using
CurrentDB.Execu te "Insert Into... to add each product record in the unbound
nested subform to the related (many) table using ProjectNr and ProductNr as
key fields. The Tag property for each option button/check box has the
ProductNr in it. The Textboxes also have the ProuctNr in the Tag property to
allow these to be associated with the relevant Product
(Optionbutton/Checkbox).

Have been trying to write code to use the TAG info and convert the info
loaded in the nested product subform by using the Insert Into query in a
loop to add the (multiple) product records to the underlying
tblProjectProdu cts. Not sure if using an array is necessary?
"Lyle Fairfield" <ly***********@ aim.com> wrote in message
news:11******** *************@g 49g2000cwa.goog legroups.com...

Probably how to read through would depend on how you created them in
the first place. You say your nested subform simulates a continuous
form? How? Is the initial data (that is displayed) part of a recordset?
Where does it come from? How many rows are on this simulated continous
form? How is this number decided? What happens when the user wants to
create a new row? What happens when the user wants to delete a row? If
you use recordset is it a DAO or ADO recordset? etc. etc etc.

[David W. Fenton]

"Allen Browne" <Al*********@Se eSig.Invalid> wrote in
news:43******** **************@ per-qv1-newsreader-01.iinet.net.au :

If you do come up with a better design that the one Access gives
you for free, please let us know.

I don't believe in using editable continuous forms, except in very
specific situations.

If I want to edit data presented in a continuous form, I use a
detail form that can be bound or unbound. This makes the continuous
form like a very elaborate listbox with lots of extra features, and
with the detail form populated in the OnCurrent event of the list
form.

Going unbound gives control over certain things, but also takes away
any number of extremely useful features (such as the .Dirty
property). I've only implemented this kind of thing very, very
seldom.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Bri]

Robert wrote:

Allen,

Started with a bound subform but switched to using an unbound subform for
better error control, more control over saving records (single button on
parent subform) and for more user friendly data capture (option buttons &
check boxes rather than combo boxes on continuous subform).

Parent subform has "Project" (one) details and nested subform has (many)
"Products" that can be selected via option buttons or check boxes and layout
of the form is not on a one record (Product) per row basis.

I understand your issue and I have a different approach to solving it. I
create a temp table (in a temp database - linked) that I then use in the
bound subform. The Save button then does an Update query that moves the
data from the temp table to the permanent table. This gives me the
flexablility that a bound form gives with the ability to save all the
changes or none of the changes (like a transaction commit or rollback
but in a form rather than in code).

--
Bri