None of the various things I’ve tried have achieved the goal, so I didn’t include the attempt to use LibO BASIC or any of the versions of the Forms which didn’t work.
If it helps, think of this as a sort of inventory problem. I thought I have been very clear in my descriptions of the task and that the task is a simple one. I intend to create was is in essence a tally sheet.
Ignoring 90% of what you wrote, here is what I gather from the above. Each “CodeGroup” should have the following associated "Code"s: xxC, xxD, xxE, xxF & xxG (where xx = same value of “CodeGroup”). Now as you are entering data, you want to know if one or more of these is missing?
I am sorry if you find this confusing. I know code E5C, for example, can only exist once in the table. It is unique. I only want to keep a count of how many times I observe a code and type it in to tally it. All valid codes are known in advance, but not all codes will necessarily be observed and counted.
In different attempts, I built both list boxes and combo boxes with all the valid codes to help with data entry of only valid codes.
(just got the comment) Your comment doesn’t really answer anything. What is being accumulated to be placed in the field “Tally”? You never answered my questions.
No, I don’t want to know how many are missing. I want to count how many times each might be entered as input data.
I had no intention of offending you by asking if you knew the word ‘tally’ and I apologize if you took offense. I would hope you pay attention to all the words (not just 10%) I make the effort to write.
No, I don’t want to know how many are missing. I want to count how many times each might be entered as input data.
I had no intention of offending you by asking if you knew the word ‘tally’ and I apologize if you took offense. I would hope you pay attention to all the words (not just 10%) I make the effort to write.
OK. The last comment may make some sense now. You have this table and every time you enter the code in a control on a form you want the counter to increase by 1?
I really am not sure how else to explain I wish to create a tally sheet.
Shall I describe what a person would do with a piece of paper and pencil?
The paper would have on it at the start the list of codes and a space to the right of each code to make a tally mark next to a code. The person is handed a stack of cards, each card has one code printed on it. The only codes the person will see on the cards are known in advance and are already on the tally sheet.
Yes! yes! for goodness sake, yes!
The form should help to permit only valid codes to be entered and increase the tally each time a code is entered. Have I not been saying that all along? That’s how a tally sheet works…
Correct me if wrong, but this “Entry” is for something completely separate from the mentioned two tables? If so, this is a critical missing piece and what has been the confusion all along.
When this person sees a code, they make a tally mark on the tally sheet next to the corresponding code.
The codes are grouped and after making each tally mark, the person can take note of the counts of all the rest of the codes in the group. The code counting does not stop until there are no more cards. Getting at least one count of each of the codes in a group is not a stopping condition.
I believe I have it. This will require a change in my sample, and I will post shortly as an Edit in my answer.
if “Entry” came from a barcode scanner, I would do that. But the codes in this task are not bar codes. They are strings of five characters. The example codes I provided are representative even if they differ slightly in detail.
I intended to type codes in, and trigger a tally increase upon hitting the key. The combo box scrolling to the relevant part of the list of codes was the best UI design. And a mouse click on a code in the list would serve as well.
Did I mention the “fun” I had for a while because I named the tally column “Count”? Oh, the hours lost to that… Well, there you have it, now I have mentioned it.
BTW - the only way this can be done is through macro coding.
Macro coding and assigning subroutines to events are familiar to me. Why it is this task would seem more difficult to accomplish than coding a GPIB interrupt handler, I don’t know.
To be clear, in no way has communicating with you been difficult. You have been remarkably responsive.
Even though I referred to many sources, read quite a bit of documentation, performed many tests using the design and debugging tools provided, and tried to make sense of the results, implementing a tally sheet has been more difficult to accomplish than I ever imagined.
I’m just glad the situation was finally understood. Hopefully the new sample provided will give you the wanted results. If not, then I’m lost again.
I’m just glad the situation was finally understood. Hopefully the new sample provided will give you the wanted results. If not, then I’m lost again.