Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

repeating controls on continuous forms

Status
Not open for further replies.

gusset

Technical User
Mar 19, 2002
251
GB
here's my setup: i have a continous form and i would like to have 10 unbound checkboxes on the form for each row of data. the checkboxes are just a GUI tool and the data of a field (hidden from the user) is dependent on which boxes are checked.

row 1 might have boxes 1 3 and 7 checked; row 2 might have no boxes checked, row 3 might have all boxes checked etc.

i want each checkbox to act independently of all the others. that is, i don't want a check in checkbox 1 of row 1 to cause a check to appear in checkbox 1 of row 2, row 3, row 4 etc, as currently happens.

can this be done (other than by having as many yes/no fields in my table as i want checkboxes, which is silly?

perhaps i shouldn't be using a continuous form...

thanks

gusset
 
You have already answered your own question....

You must either not use the continuous form or put all the checkboxes in the table. This is because Access only sees the controls in the continuous form as one set...there are not separate ones for each record. So any UNBOUND control will affect all shown controls on the form....BOUND controls ar not subject to this restriction.

****************************
When the human body encounters disease it raises its temperature making it uncomfortable not only for the body but also for the disease. So it global warming the Earth's way of saying we are not wanted?

Robert L. Johnson III
MCSA, CNA, Net+, A+
w: rljohnso@stewart.com
h: wildmage@tampabay.rr.com
 
I just dealt with a similar situation. I had a linked table (which I was unable to modify), and I wanted to display the records on a continuous form, while allowing the user to select which records would be processed when a button was pushed.

The way I did this was by creating a table in my front-end which contains two fields, a yes/no field to signify if the record was selected, and a primary key field that matches the primary key field of the linked table. I then created a one-to-one relationship between the tables with a right join between my temporary table and my primary table.

When my form starts up, it sweeps through the recordset setting the selected field to false. This creates records in my temporary table where necessary. There is a check box linked to this selected field, which allows the users to check the fields they want.

This is an overly simplified description, but hopefully it may give somebody else an idea on how to accomplish this in their project.

 
We were displaying a large number of fields, and allowing the user to select fields to search on to limit the records displayed. After limiting the records displayed, the user could then select which records to process. Although a list box may have worked (I'm not sure either way), the interface wouldn't have been as easy to use or implement (in my opinion).

I did consider that as my next option if my idea hadn't worked.


 
KornGeek, just wanted to say that your solution was very elegant and i wish that i had thought of that!

best wishes

gusset
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top