I don't, as these days the applications are all just for me and my wife to use so it's not a problem, as the interface opening is merely an inconvenience.
And I seldom use reports: I send almost all my printing output to Word documents (personal preference). You don't need a print button on the report anyway as CTRL-P does the business.
I don't, as these days the applications are all just for me and my wife to use so it's not a problem, as the interface opening is merely an inconvenience.
And I seldom use reports: I send almost all my printing output to Word documents (personal preference). You don't need a print button on the report anyway as CTRL-P does the business.
Fair enough though using /runtime seems superfluous in your situation
The reporting feature in Access is very powerful. I'm intrigued by your personal preference of outputting to Word. I assume you do that using automation or mail merge
Fair enough though using /runtime seems superfluous in your situation
The reporting feature in Access is very powerful. I'm intrigued by your personal preference of outputting to Word. I assume you do that using automation or mail merge
Years back when producing output for real, particular circumstances meant I needed Word documents for other usage and I got into the habit. If producing a huge output then reports ARE quicker, but that is seldom my requirement. I use automation which gives me a far finer control over output formatting a word/character level and treating specific anomalies, according to circumstance.
To put it in context when I retired and started only using Access for fun, everyone was on 2003 corporately and output options were more limited. It's now all for fun.