Continuous unbound form

[Question Boy]

I have a table that list various products. I now want to create a dynamic
continuous form that when opened will list each of the products to permit
data entry of other related information. I tried building a function on open
that loops through the table records and populated a new record in the form,
but since it is unbound this didn't work. How can I o about it? Something
tells me I'm missing something really obvious!

Thank you

QB

 

[Klatuu]

No, you aren't missing anything obvious.
The issue is that even though you see multiple instances of a control on a
continuous form, there is really only one instance of the control.

Why not use a bound form?

 

[Question Boy]

Could you explain a bit more please. You wouldn't happen to have an example
I could look over by any chance?

QB

 

[Klatuu]

There is no example to look at. You can't do what you are trying to do.
What I was trying to explain is the reason you can't do it in an unbound
continuous form is because an unbound continuous form really only has one row
and you can't add rows to it programmatically.

Again, why not use a bound form?

 

[Question Boy]

Sorry for not following your train of thought.

I need to allow the user to enter it one way and transform the data into
another format for storage. I'm trying to bridge their work methodology with
the existing system.

They enter data like # at start and # at end but the database only track the
delta value so I was trying to build a form that would list all the items and
allow them to enter the Start and End values and then append the Delta value
to the appropriate table.

QB

 

[Klatuu]

Okay, I see what you are trying to do.
You can still use a bound form. Create a table to hold the data the way
they enter it. Then they start out with a continuous form bound to the table
fields.
When you are ready to transform the data, use the data in the table to do
the transformation, then delete the data from the table so it will be empty
for the next use. Now, if this is a multi user application and you are doing
it correctly with a split back end and each user has his own copy of the
front end, I would suggest you put this table in the front end so if more
than one user is entering data in the form at the same time, they will not
interfer with each other.