Generating or getting the code behind a report

[SPSUSteve]

I've created a report using the wizard then fine tuned with the drag and drop method. I know how to get into the code window and add code behind the scenes and consider myself a decent programmer (probably intermediate with VB, I typically use PHP for my web apps).

I want to see the code that is behind the scenes of the report. Is there a way to do that? Not the code that I write, but get to the code that the GUI wrote.

 

[dhookom]

There is no exposable code behind the report that gets generated in a report unless you put some there.

Maybe someone could provide more assistance if you described why this would be important to you.

Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[SPSUSteve]

I was hoping to use the GUI to start the report and then fine tune it with the code (which is possible, except when I get stuck . Reading the code that is there might help me to determine where and how to add my own when I get stuck.

So it seems I have two possibilities:
1) just as I said above, use the GUI to drag and drop obejects, then modify with my own code as necessary or
2) create my own report completely from code using the print method. Which would mean that I have to explicitly position each object, control, etc. which is really what I'm trying to avoid.

 

[dhookom]

I have done both 1 and 2. The second choice is a bit of a pain. I start with a mostly blank report and use the Print and Line methods to add "content".

I have some calendar/week-at-a-glance type reports at

http://www.access.hookom.net/Samples.htm

which use code in the On Format or Print events to move and resize controls.


Duane MS Access MVP
[green]Ask a great question, get a great answer.[/green] [red]Ask a vague question, get a vague answer.[/red]
[green]Find out how to get great answers faq219-2884.[/green]

 

[SPSUSteve]

I'll take a look. Thanks for the reply.