As a general rule that "automatic" creating of a report is a quick and dirty option.
As a general rule?
You want to create the report BEFORE you start using code. So, create the report, lay it out the way you want. Add the fields, set page layout landscape or normal. This goes "on and on" for some time.
Once you have the report the way you want, you save it, and now can launch that report anytime you want.
docmd.OpenReport "myReportName", acViewNormal
So, that option I think only grabs the first 15 fields. it not really a "program" feature, or something that developers would use in code (not really sure why they have that option). But it gives you ZERO control over the layout - and I think it only pulls the first 15 fields anyway (or puts additional fields on the next page). All in all - it not really a useful nor practical option.
So, create the report BEFORE you start using and writing code. Get the report the way you want and then save it. Once you have that great looking report, then you can certainly say have a button or code in a form or such some to launch + display the report. But allowing the "default" create of the report with that option simple does not give you much if any control over the results and things like only 15 first controls etc. are of course "minor" to the overall limitations of such an approach.
Worse, is each time you run that command, a whole new report is created - and once again you have little to next control over the results.
So, build the report first - use the access UI part, and then after you get the report JUST the way YOU want, save it, and then use that along with the openReport command as per above.
Regards,
Albert D. Kallal (Access MVP 2003-2017)
Edmonton, Alberta Canada