Dynamically numbering

Therat

Access Denied
Local time
Today, 14:22
Joined
May 21, 2002
Messages
53
I am trying to create an access report that looks like the attached word document. The difficulty I am having is trying to get all the data on one page. The projects that I and my teammates worked on last week don't necessarily link to the projects we will work on next week. The data sits in one database.

I had this idea that I could dynamically number each row by employee in two different queries, "thisweek" and "nextweek" (<--Please help with this part), use a union query, and link unique numbers together so I could build a report with a similar look to our old word report. Any ideas how to dynamically (in a query or else) number each unique projects by employee in these two queryies?


Thanks in advance!
TheRat
 

Attachments

  • weekly report.JPG
    weekly report.JPG
    57.5 KB · Views: 156
You can probably achieve the side by side look using 2 subreports, one for this week and one for next. I don't think I understand your db structure well enough to offer specifics on the queries.
 
Thanks, but....

I tried the subreport route, but bc of the dbase structure it will put each week on a different row. Here are the fields in the dbase: majorprojects, employee,weektype (<--thisweek or nextweek), deadlines, currentdate, busunit, serviceline, and deliverables.

The reason it puts it on different lines is the column weektype and the fact that there isn't necessarily a match between thisweek and nextweek. If I could dynamically number each row by employee in two different queries, "thisweek" and "nextweek", use a union query, and link unique numbers together, I could build a report with a similar look to our old word report.

Any ideas?!?
TheRat
 
I'm a little confused by "Weektype" being a field, since I would assume that would change with time (and be calculated as needed). Today's "Next week" project will be a "This week" project next week, won't it? (I even confused myself with that one). Do you run a process to change that field periodically, or am I misunderstanding the whole concept here? What are the chances of a sample db with data in it that you would want coming out like your word report. I envisioned the 2 subreports, one restricted to "this week" project, the other to "next week" projects.

There are lots of examples of adding a numbering or ranking field to a query, but I don't understand how that helps here.
 

Users who are viewing this thread

Back
Top Bottom