Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 191
  • Last Modified:

Design - Responses

I have a database with a Job main form and a EmployeeDuties response form. We create a Job form for each job and then create EmployeeDuties as responses for each employee working on the job.

I can happily create a view which lists the jobs and the employees working on them, and their duties. What I now need to do is the reverse. I need a view of all EmployeeDuties forms (first column employee, categorised) with the Job's they have worked on listed for each. So I would have the EmployeeName field categorised, several fields from the Job doc, some of which will be categorised, followed by the DutiesDescription from the EmpDuties form.

1/ Is this possible if I have the given form structure?

2/ In the past when I've needed this funcionality, I've made both forms Docs (not responses), and then built the views. It works but is complex. So, os there a better way to get this result?

Thanks
0
gbentley
Asked:
gbentley
  • 3
  • 2
1 Solution
 
CRAKCommented:
1st you need to DEselect the view's option "Show responsedocument in hierarchy".

With 1 Job having multiple duties, I assume you want the job shown under each of the duties. It'll be hard to show the job a number of times, depending on the number of duties. The only way to do that is to update the job document after processing a duty: store the names of each of the job's duties on the job. Show them in the view with the option "Show multiple values as separate entries" selected.

Now you have to group and sort the right documents. Create a hidden (1st) column for that, showing the duty (for both the job and the duty!) and concatenate a "1" for a duty or a "2" for a job. Sort that column.

Disadvantage: you cannot expand/collaps the view.
0
 
gbentleyAuthor Commented:
Thanks.

I've gone back to doing all the updating in script and not trying to use the Response system. There goes another days work!
0
 
CRAKCommented:
Try to see that as a positive thing....
Too many people in IT go unemployed lately!
0
 
gbentleyAuthor Commented:
It's part of the game!

Remember - "Plan on throwing the first draft away"
0
 
CRAKCommented:
I remember on one assignment all people could talk about was RAD and DSDM. So we started: time-boxing, prototyping, reviewing, improving etc.
Generally the 1st prototype got slammed and battered long enough to meet ALL requirements. Even when we adviced half-way to start over again and leave the trach of patching.
Then... one day they invented something "new".... the DISPOSABLE PROTOTYPE!
;-))
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now