create a new record - reporting database -

[Analyst12345]

Hi,
I am designing a new database to build regular reports on different projects.
There is a project table where data is about the particular project.
Related to that table, there are an Issue table and a status table.



Every project can have many status items and issues.
The status table and issue table will be updated every week.
I am looking for a way to create a database where the project manager pulls the information from the previous report, and updates the information for the current reporting period by creating a new record for a particular issue / status item without overriding the previous week data. This way, every week's data still exists.
I am looking for a solution that I can do with macros as I don't have a lot of experience with coding.
Thank you!
Analyst12345

[Bulzie]

Sounds like your main form will be Projects and you will have 2 subforms for Issues and Status linked to Projects(use LinkMaster Linkchild). So after he pulls up the project, it will show all the Issues and Statuses in those subforms and also allow him to add new Issues/Status for the current week in those subforms. Just add a date field to each of your Issues/Status subform records.

[ssanfu]

Without some examples of the data, is the status table for a particular project or is the status table for a particular issue.


Project -->>Status


Project -->> Issue -->> Status

[Analyst12345]

It follows this one " Project -->>Status " . Each project table for issues, and a table for status. there is no relationship between issues and status. the relationship are all from the project table to other ones.

[orange]

You need to get your tables and relationships designed to meet your "business requirements", and that isn't clear from your posts.

Is it a Project that has a Status? Is it an Issue that has a Status? Is it Projects that have 0,1 or more Issues? Your 3 tables do not exist in isolation.

Give us a description of a typical Issue, Project and Status scenario from your business operations in simple, plain English.
Forget your current tables and please no database jargon --just simple English.
Once we're all on the same page there will be more focused responses.

Good luck with your project.