Allowing Editable Data

gary.newport

Registered User.
Local time
Today, 11:44
Joined
Oct 14, 2009
Messages
79
I have a cross tab query that I am basing a continuous form on. I have a number of issues arising from this:

The first relates to the fact that in the crosstab is a field that is set to Yes/No. It appears as a textbox with a value (0 or 1) in it. I want to replace this with a tickbox but when run neither the textbox nor the tickbox will allow any changes. Is it possible to set this to be editable? I cannot see how this would relate back to the actual data table but if it is possible then this should become clearer.

The second issue relates to the fact that the crosstab obviously creates the number of columns in relationship to the maximum number of values of the relevant field. So, I have a field that can have values from 1 to 15 but in most cases the actual value runs no further than 9 and 10. So for those records where the maximum number is not being used I want the unused tickboxes NOT to appear. Again, is this possible.

In connection with the second, if I have (as I do) this group of 15, which is in fact made up of 3 groups ranging from 1-8, 1-4 and 1-3. So number 8 may not be required in the first group and numbers 3 and 4 in the second. I would prefer there not to be a strange gap between the datasets when run. Is it possible to set up a continuous form so that all the potential boxes are in place, that I run code on load that puts the values in from the query, hiding the end tickboxes and so collecting the groups together - then allowing the changes to be detected through code and re-assigned to the table?
 
1. If you use a CheckBox as you have described, how do you plan on enabling it so you or a user can edit again? Seems to me like a Security Level thing or a password driven issue!

2. Using a If statement would assist with this. Example;
If DCount("[PrimaryKey]", "tblMyTable") >10 Then
Me.SomeField.Visible = False
Exit Sub
End If

Hard to know without more details.

HTH
 
No issues. Most of this has now been solved (I think).
 

Users who are viewing this thread

Back
Top Bottom