Prompt for report name

[kitty77]

Is it possible to get prompted to enter the report name instead of what I'm using?

strDocName = "Report-BA"
DoCmd.OpenReport strDocName, acViewReport, , strWhere

Thanks.

 

[MarkK]

To the question, it is possible? Yes.

 

[kitty77]

Could you provide me with an example?

 

[plog]

You should be able to make the title box on the report unbound and then assign it a name not in the underlying datasource:

Set it's control source to:

=[Enter Report Name]

 

[DHookom]

I agree with Pat. I would not use prompts for anything is Access including object names, InputBox(), and query parameters. The closest I come to prompts is MsgBox().

 

[GPGeorge]

I agree and here's why.

People are really good at recognizing and interpreting patterns. We are not so good at remembering exact details. (e.g. is that report name "rptQuarterlyMaintencebySector", or rptQuarterlySectorMaintenance"?) We can remember it has something to do with a time period, an activity and an area.

Computers, on the other hand, and Access specifically, are really, really good at the details. One letter off in a report name and it no longer matches as far as Access is concerned.

That's why I don't open a parameter input box and ask users to remember the details about the name of the report. That's why I show the user a combo or list box with a familiar name they can spot easily, and a hidden column for the specific report name Access needs to do its job.

 

[tvanstiphout]

Computers, on the other hand, and Access specifically, are really, really good at the details.

Is there a lesson to be learned in your misspelling of "maintenance"?

 

[GPGeorge]

Is there a lesson to be learned in your misspelling of "maintenance"?

You caught me. Yes, Spelling Counts, and that's a significant part of the message.

 

[DHookom]

George meant to do that as a lesson to us all

 

[Cotswold]

Basic rule number number one of programming: Totally control the users and stop them from messing the job up.
This is the total opposite. You'll spend hours on support calls with idiots telling you over and over they've definitely typed the name correctly.

 

[The_Doc_Man]

@kitty77 - as you can see, the opinion here is overwhelming - and based on an accumulation of probably over 100 years of total experience (if you include me). Your better choice is to give your users an explicitly spelled-out chance to choose from a list rather than giving them a direct input ability that has good odds of causing an error to pop up because of possible errors in the name.

If you think your users will be unhappy for not having the chance to type in a raw, unfiltered name, just think of how irate they will be when Access takes a fatal error because it pops up the dreaded Debug-or-End Program box - from which the only recovery is to close Access and start over again.