Dynamic reports from an .mde database

[Max Moor]

Hi All,
I have a number of reports that I set up in design view (hidden)
before displaying them. I just converted my front end to an MDE file, and
now I can open them in design view. If I[d have thought about it, I'd have
realized this before it ever happened.

I thought I could put the dynamic reports in the backend, but don't
see how to link to a report. Also, this solution, if it's even possible,
leaves the report's design and code visible.

So, how can I do a dynamic report? I have to have my front end as an
MDE, but some reports just need to be forrmatted at run-time. What's the
preferred method for having it both ways?

Thanks for any and all advice...

Max

 

[Marshall Barton]

I have a number of reports that I set up in design view (hidden)
before displaying them. I just converted my front end to an MDE file, and
now I can open them in design view. If I[d have thought about it, I'd have
realized this before it ever happened.

I thought I could put the dynamic reports in the backend, but don't
see how to link to a report. Also, this solution, if it's even possible,
leaves the report's design and code visible.

So, how can I do a dynamic report? I have to have my front end as an
MDE, but some reports just need to be forrmatted at run-time. What's the
preferred method for having it both ways?

I suppose you could use Security to make the objects
unavailable, but I've never tried to go down that twisty
road.

The usual approach is to setup the reports in design view
with all the controls and sections that might be needed,
then use the code in the report's Open event to make the
needed ones Visible and adjust their other properties
according to whatever you're using to determine how to
create it from scratch. In my experience, it actually takes
a little less but very similar code to what you've been
doing.

 

[Max Moor]

The usual approach is to setup the reports in design view
with all the controls and sections that might be needed,
then use the code in the report's Open event to make the
needed ones Visible and adjust their other properties
according to whatever you're using to determine how to
create it from scratch. In my experience, it actually takes
a little less but very similar code to what you've been
doing.

Hi Marsh,
I've found that I can do that for almost everything. The hitch (I
think) is that the form's Width property can only be changed in design
view. Ultimately, I want to be able to adjust the width based on whether
the Printer is set to Portrait or Landscape. In retrosect, I didn't ask
the question very well, since this is really the only problem. Maybe the
Width property isn't the right answer in the first place for this? If you
know, I'd be grateful to hear what you know. Otherwise, maybe I should
post a better question.

Thanks, Max

 

[Marshall Barton]

Marshall Barton wrote

I've found that I can do that for almost everything. The hitch (I
think) is that the form's Width property can only be changed in design
view. Ultimately, I want to be able to adjust the width based on whether
the Printer is set to Portrait or Landscape. In retrosect, I didn't ask
the question very well, since this is really the only problem. Maybe the
Width property isn't the right answer in the first place for this? If you
know, I'd be grateful to hear what you know. Otherwise, maybe I should
post a better question.

Gee, Max, adjusting the report's Width is a tough one -
AFAIK, there's no way to do it. As much as I hate
suggesting it, I would go with two reports, one for portrait
and one for landscape. What the hey, their layout probably
has enough significant differences that might even make it
advantagous?