Individual controls for each record

dc_sc

Registered User.
Local time
Yesterday, 22:04
Joined
May 30, 2003
Messages
24
I have a continuous form based on a query. I would like to have a button or control that performs some command on only one certain record. In other words, the user sees the record he wants, clicks a button and it changes the value or changes the color. When I add a button to the form, it appears next to each record and performs the same command to each record. I have tried different controls, but get similar results with each one. Even a single form seems to do the same thing, but on different pages.

Am I missing something? Or maybe I am not following the concept of the form.
 
dc_sc said:
Am I missing something? Or maybe I am not following the concept of the form.

The concept is that continious forms can be a pain in the ass. You aren't doing anything wrong, just the stupid way they are. :mad:
 
Oh, that's not what I wanted to hear. Any other ideas to accomplish the same thing? The bottom line is: I want the user to be able to view several records from a table or query and be able to select certain record(s) and perform a function like an append to another table with just those records. I want a form because I want to customize the appearance of the data. Imagine a check register showing all of the checks you wrote today and you want to click off certain ones that were paid. That would, in turn, subtract those checks from your main check ledger and the form would just show those that are still pending. That's the best I can explain it. There must be a way...
 
G’day dc_sc

Nearest demo I had lying around.

The trick is that the check box, and there is only one, needs to be bound to a field.

Hope that helps.

Regards,
Chris.
 

Attachments

That looks like exactly what I want. I see that the check box is coming from the table. If the table I am using does not have a field like that, is there a way to add one with a query?

Thanks so much for your help
 
Possibly, I never tried it.

Question though, would you want the state to be persistent between form sessions or would you require it to be set back to unchecked at each form/query run?
 
Are you able to add a field to the table directly? Or is the data coming from a source other than access?
 
G’day dc_sc

Well now that I’ve tried I must say I could not get it to work in a query but that of course doesn’t mean it can’t be done.

What it appears you are trying to do may not need to be done at all. It appears you have a table of unpaid checks, the user clicks on one or more checks and they are transferred to another table.

But why transfer them to another table at all?

It would seem that when one is paid there would be other information that would need to be saved, such as the pay date. Therefore it would seem that the check box is not required only a pay date and queries could be built to return all checks with a pay date or, conversely, all checks where the pay date is null.

So, if I’m not seeing it in an oversimplified manner, the paid field in the table would be a boolean duplication of the pay date field being null.

Another less important consideration may be that when the paid check information is deleted, from the unpaid table, Access probably won’t reclaim the used space till a compact is done.

Might be better to keep all checks in the main check ledger, paid or not, and simply mark them with a pay date.

Probably an oversimplification on my part???

Regards,
Chris.
 
Put a button on the FormHeader

One cool solution here is put a button on the header of your continuous form. Make sure RecordSelectors = True so the current record is indicated by the little sideways triangle. Then when the user clicks the button, your form's fields, like Me.SomeField will contain the values of those identified as the current record. Turns kludgy continous forms into super cool continuous forms.
 
Won't work for colours though

Changing the colour of a control on a continuous form must change the colour of ALL the controls on the form, but this is not so for data.
 
Technically incorrect.

Changing the colour of a control on a continuous form changes the colour of all instances of that particular control not all controls on the form.

Some may read this as semantics, but semantics is the way it is read.
 
ChrisO, I think I understand what you are saying. First of all, I cannot alter the original table from where the data derives, however, I have made a new table and added the "date paid" field as you suggest. SO I can bind that field to the form as a null value, but then how can I create some control to insert the date/time into that field for those certain records that I select?

Lagbolt, I did not quite understand your current record idea.
 
I mentioned semantics in a previous post, and this is the reason why: -

First up we sometimes need to ‘back-off’ from preconceived ideas, they can simply cloud the issue.

Next you say you cannot alter the original table but have achieved a "date paid" field.
(That is in itself incorrect because it has a space in the name.)

Next thing to ask is how did you create a field in a table that you can’t alter? Did you create a new table with a one-to-one relationship? If so, what primary key did you use?

Next thing to ask is; can something be paid for in multiple payments? To put that another way; if payment by installment is possible then a single payment date is not enough, we would need a one to many relationship between total payment required and installments.

Next thing to ask is; can any payment be ‘marked off’ to a particular charge or can they run a ‘tab’ on total payments and, thereby, marking off payments to a total outstanding account?

Next thing to ask is; how does the user ‘back-out’ of some ‘indiscretion’?

The answer would seem to lie in business requirements, not in how to format a continuous form…that much is easy.

The formatting of a continuous form requires a boolean result as the condition, not some vague undefined variable... everything else comes first, then the formatting.

Maybe it’s just semantics…but semantics is the way it works.

Regards,
Chris.
 

Users who are viewing this thread

Back
Top Bottom