RecordSource Using a PassThrough Query

[Chris]

I have a form that I change the record source for using a passthrough query.
This works fine but now I need to be able to bring back more than one record.

Using Code I actually create the Passthrough query and save it the queries
tab, then assign the form fields to the value of each corresponding field in
the query. I want to be able to scroll through each row in the query. I also
want to leave the form fields unbound because I need to use these fields to
run another pass through query that updates the back end database.

Any ideas is much appreciated

Thanks

-Chris

 

[Dirk Goldgar]

I have a form that I change the record source for using a passthrough
query.
This works fine but now I need to be able to bring back more than one
record.

Using Code I actually create the Passthrough query and save it the queries
tab, then assign the form fields to the value of each corresponding field
in
the query. I want to be able to scroll through each row in the query. I
also
want to leave the form fields unbound because I need to use these fields
to
run another pass through query that updates the back end database.

Any ideas is much appreciated

I'm not sure I follow you, but you can have a bound form with unbound
controls. In that case, the normal record-navigation buttons will work (or
you can build your own, which would manipulate the form's recordset), but
you have to use code in the form's Current event to load up the unbound
controls from the corresponding fields.

 

[tkelley via AccessMonster.com]

"I also want to leave the form fields unbound because I need to use these
fields to
run another pass through query that updates the back end database."

I'm not sure I understand why you can't use the bound field values to pass to
another pass-through.

But I'll take your word for it, and assume I don't know the whole picture.
So here is an idea ... What if you have two controls for each field, one
bound and hidded, one unbound.

So if you have a bound Control, [BoundControl_1], you'd have another unbound
with this in it's control source: =[BoundControl_1]