I have existing data that shows a document that has been routed for assessment by various work groups, the date it was sent to them, when it is due back and when and if they have returned it. I want to have a record for each work group as they want to track them separately. I’d like to have a form where you check or select via pull down every work group effected and then have that table get updated with a record for each… Is that possible?
Suppose I have a form with a list box (named "lstWorkGroups") that is populated from a workgroup table with their names in it (and the primary key of those name records).
Suppose this form has a record of some data that requires action and it is bound to a table named "tActivity". Sometimes it is for one workgroup, sometimes it could be for multiple workgroups.
Now supposing there is another table that the workgroups look at to see if there is any action and that table is called "tWorkGroupActivities". This table could potentially be filtered so the workgroups only see items intended for their view only.
Some data comes into the database and hits tActivity. A user then selects some workgroups out of the list box and clicks a command button called "Go".
If we wanted the system to then copy the record in tActivity and "assign" it to the workgroups selected, the code behind the button would something like this:
Code:
...
Well, it would probably be easier just to post something for you
to analyze and to confuse all of mankind.
...
I've used the above scenario I typed out. If you click on the the form, fActivity, is the one with all the action. Look at the code behind it to see what is going on.
I included the form fWorkGroupActivities which is based on the query just for grins. It is so you can cycle through as an excercise in imagineering to create the different workgroup views. The idea here is that the workgroup can see the stuff on the Activity form and make any changes they are supposed to.
The last form is not required, it seems you have that part licked.
The demo isn't designed for normalization because I am not really sure of the overall goal you are trying to accomplish and it doesn't have all the error checking or data validation (is there a date inputted?, did the user select something?) - I am leaving the overall design, error checking and data validation to you - this was just a proof of concept to help you along.
