Good Morning,
I am working on a project where I have a view that is shared with a table (bound to SQL) and an embedded view that is a selection panel.
For context, this is a process that has 3 stages that has 3 operators that can not see one another. The idea is that when an operator is working at a certain station (either station 0030, 0040 or 0050), they would then select the operation and defect code, then select the total they have when they are scrapping a product, and then select add. This will add it the SQL table that is being shared.
Likewise, if they wanted to delete a row from the table, they would just select a row and select delete, and the row would disappear.
So this view/project will be used by three separate clients on three different 3 users that will have there own tablet PC.
The thing I am wanting to achieve is to have the selections panel be custom to what the operator for that station has selected. This means that at any one time, each of the 3 operators could have different operations and defect codes selected with their respective totals that only they can see. Once they have added it to the table, all stations can see what is added.
The tags that have values in the selection panel are Operation, Defect code, and Total.
Any help would be great.
Thanks Ryan,
Good night!
[Text no longer relevant after OP updated.]
hi @Transistor apologies I have updated the post. Please let me know if that makes sense.
Regarding your questions:
Do you mean "this view / page will be used by three separate clients on three different PCs"? - Yes
Surely you only present them with options based on their login or what machine they are working on? Do they log in? - No can do at this stage as.
No can do at this stage as.
Um ...?! As what?
You need some way to determine who is logged in or what machine is being reported on. It seems to me that your SQL table should also have a column for that information and then the query only returns relevant records for that session. That should make it very easy.
So currently, what you haven't seen is that there is a checklist at the beginning, prior to this screen, that asks for all the operators who work on this production order during this shift to enter their ID number at the begining of the shift. But during the shift, you can have up to 9+ people cycle through this process, so at the beginning of this solution, I did not consider what you were saying as I wanted to make it easy for people to jump on and use.
It sounds like some rethinking is required.
Write a user requirement specification for yourself and then see if you can figure out how to meet it!
