Hello.
We all know I'm a basic bitch.
Good. Glad that's out the way.
I'm trying to put a procedure in place so that I can delegate the production of a report to others, so if/when I leave I know things will still work nicely. this follows on from the guy who left after programming everything (>60k lines of VBA code, no comments, no SOP to help people, nice person).
I've got a union query that joins three tables together to get all cases from 2015 - 2016.
I've got a make table from that union query that also has an ugly IF statement in to produce two new columns.
I've got a query that looks at the table generated above and only takes out columns I want (leaving behind the IF statment columns).
Can I join all of those queries together into one SQL query? Typically, this is my train of thought of having modules to do things, rather than one overall routine. Because I'm a basic bitch.
I don't want to use a macro because that generates the whole "click button do work" rather than "think about what we're doing here". So if I'm gone, nobody will be able to use the routine.
I've then got a spreadsheet that plots graphs and does stuff like counts cases per month in the different areas. This looks at the final table generated in access. The graphs are nice, the tables i've generated are laid out nicely, and have lovely sparklines.
The contents of this spreadsheet are required for a report are linked to a powerpoint document. So headers update with dates, text can be changed in the excel sheet and is then updated in the powerpoint thing.
It feels a bit overly complicated, but it works.
Extract data, run 3 things in access, close access, open excel, refresh/calculate formulas, open powerpoint, print to pdf, circulate.
Is there a way, there must be, to increase the efficency of the data table generation in access?
Hello.
We all know I'm a basic bitch.
Good. Glad that's out the way.
I'm trying to put a procedure in place so that I can delegate the production of a report to others, so if/when I leave I know things will still work nicely. this follows on from the guy who left after programming everything (>60k lines of VBA code, no comments, no SOP to help people, nice person).
I've got a union query that joins three tables together to get all cases from 2015 - 2016.
I've got a make table from that union query that also has an ugly IF statement in to produce two new columns.
I've got a query that looks at the table generated above and only takes out columns I want (leaving behind the IF statment columns).
Can I join all of those queries together into one SQL query? Typically, this is my train of thought of having modules to do things, rather than one overall routine. Because I'm a basic bitch.
I don't want to use a macro because that generates the whole "click button do work" rather than "think about what we're doing here". So if I'm gone, nobody will be able to use the routine.
I've then got a spreadsheet that plots graphs and does stuff like counts cases per month in the different areas. This looks at the final table generated in access. The graphs are nice, the tables i've generated are laid out nicely, and have lovely sparklines.
The contents of this spreadsheet are required for a report are linked to a powerpoint document. So headers update with dates, text can be changed in the excel sheet and is then updated in the powerpoint thing.
It feels a bit overly complicated, but it works.
Extract data, run 3 things in access, close access, open excel, refresh/calculate formulas, open powerpoint, print to pdf, circulate.
Is there a way, there must be, to increase the efficency of the data table generation in access?