Display multiple records on a single form

[Guest]

Hello,

I have an access/vba application I'm trying to extend. I'd like to create a
new form in which several records are displayed, followed by an edit and
delete button. A textual representation of what I'd like is as follows:

Person ID - 123456
Order ID - Product ID - Quantity
ord123 - prod123 - 4 [EDIT BUTTON] [DELETE BUTTON]
ord234 - prod234 - 3 [EDIT BUTTON] [DELETE BUTTON]
ord345 - prod345 - 5 [EDIT BUTTON] [DELETE BUTTON]
....

The number of records will be dynamic because each individual will
potentially have any number of records which I'd like to display on a single
page. Can anyone provide me with some tips as to the best way to implement
this type of form and possibly some sample code (or a URL to some sample
code)? I'm relatively new to access development, so I'm not even sure what
controls I'd need to use to facilitate this functionality, so any advice
would really be appreciated. Alternatively, if someone has another
suggestion regarding how I can go about implementing this functionality I'm
all ears.

Thanks a lot,

Melissa

 

[Guest]

Melissa,
Multiple record is easy. Set the form's Default View property to Continuous
Forms. This displays all values in the detail section, with a row for each
row in the table. Add two command button on the right side of the detail
section. If you have the control wizrd turned on, it will prompt you for how
what action you want it to take(the control wizrd is activated with a button
that looks like a magic wand). You want Record Operations, Delete Record for
the delete button.

I'm not sure what you want your Edit button to do. If the form is bound, the
user will be able to edit the records by default. Do you want to lock out
edits until they press this button?

Barry

 

[Rick B]

Melissa:

Please stick to one post.

http://www.mvps.org/access/netiquette.htm

 

[Guest]

Hi Barry,

Thanks for the tips. What I was thinking for the edit button is that the
user would be redirected to the same page they used to create the order, but
with all the fields populated with data from that particular order. I
suppose this is not required if the orders are editable on the page that
displays all the records.

To get a series of records to display on the form, do you have to bind a
recordset to the form after you set the default view to continuous forms?

Thanks again,

--
Melissa

Melissa,
Multiple record is easy. Set the form's Default View property to Continuous
Forms. This displays all values in the detail section, with a row for each
row in the table. Add two command button on the right side of the detail
section. If you have the control wizrd turned on, it will prompt you for how
what action you want it to take(the control wizrd is activated with a button
that looks like a magic wand). You want Record Operations, Delete Record for
the delete button.

I'm not sure what you want your Edit button to do. If the form is bound, the
user will be able to edit the records by default. Do you want to lock out
edits until they press this button?

Barry

Hello,

I have an access/vba application I'm trying to extend. I'd like to create a
new form in which several records are displayed, followed by an edit and
delete button. A textual representation of what I'd like is as follows:

Person ID - 123456
Order ID - Product ID - Quantity
ord123 - prod123 - 4 [EDIT BUTTON] [DELETE BUTTON]
ord234 - prod234 - 3 [EDIT BUTTON] [DELETE BUTTON]
ord345 - prod345 - 5 [EDIT BUTTON] [DELETE BUTTON]
...

The number of records will be dynamic because each individual will
potentially have any number of records which I'd like to display on a single
page. Can anyone provide me with some tips as to the best way to implement
this type of form and possibly some sample code (or a URL to some sample
code)? I'm relatively new to access development, so I'm not even sure what
controls I'd need to use to facilitate this functionality, so any advice
would really be appreciated. Alternatively, if someone has another
suggestion regarding how I can go about implementing this functionality I'm
all ears.

Thanks a lot,

Melissa