Why do you need to create a report at runtime? You can change Recordsource, ControlSource etc value at runtime for an existing report, so if you want to provide a more "dynamic" experience to endusers, you can do so with a lot less aggravation by using tried and tested techniques (as discussed below).

Creating reports at runtime is a never a good idea unless there is no other way around it (and in 10+ years of coding, I've yet to see no other way around it). You would be far, far better off creating your report in Design view, then modifying that report as needed during runtime.

In order to create a report, you must create the actual report then open that report in Design view and add and position your controls (using CreateControl and the various properties/methods of those controls) ... add any sorting/grouping to the report ... add headers/footers ... add code (if need be) ... add formatting to the report (i.e Fonts, colors etc) ... all of this while your user sits and waits while the app is churning away. And, after you do all this a couple of times, your application will be decompiled (since adding an object will decompile your project), horribly bloated and almost certain to corrupt.

In other words, take the advice of those who have traveled this road before - just say no <g>, and build your report during Design and manipulate it (if need be) during runtime.