By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,663 Members | 1,792 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,663 IT Pros & Developers. It's quick & easy.

DoCmd.PrintOut .... Doesn't

P: n/a
Question about DoCmd.PrintOut in A97.

I have a form on which all the controls are unbound. There is a large
textbox that the user can type stuff in and a couple labels. I am trying
to code a Print button to simply print out the form.

Problem is, DoCmd.PrintOut only produces a blank page. (Actually once in
testing, it printed the form module's code, but not the form.)

In another app I am working on, PrintOut successfully prints the form
and data. The difference, or at least the obvious difference to me, is
that in the other app the form's controls are data-bound.

Does this seem like a limitation of the PrintOut method? I have not seen
any indication of this in the help file, but wondered if anyone else has
had the same experience.

Thanks for any suggestions.

I am posting another question separately about a potential work-around
using a report to take care of the printing.

This is an awesome group, BTW!
--
Smartin
Nov 13 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On Wed, 26 Oct 2005 18:19:35 -0400, Smartin <sm********@yahoo.com> wrote:
Question about DoCmd.PrintOut in A97.

I have a form on which all the controls are unbound. There is a large
textbox that the user can type stuff in and a couple labels. I am trying
to code a Print button to simply print out the form.

Problem is, DoCmd.PrintOut only produces a blank page. (Actually once in
testing, it printed the form module's code, but not the form.)

In another app I am working on, PrintOut successfully prints the form
and data. The difference, or at least the obvious difference to me, is
that in the other app the form's controls are data-bound.

Does this seem like a limitation of the PrintOut method? I have not seen
any indication of this in the help file, but wondered if anyone else has
had the same experience.

Thanks for any suggestions.

I am posting another question separately about a potential work-around
using a report to take care of the printing.

This is an awesome group, BTW!


Forms are for viewing, Reports are for printing.
Create a report which displays the same data as your form. Use your print button to print the report for the selected
record.

DoCmd.OpenReport "rptMyReport",,,"(MyIDField)=" & Me.MyIDField
Nov 13 '05 #2

P: n/a
Wayne Gillespie wrote:
On Wed, 26 Oct 2005 18:19:35 -0400, Smartin <sm********@yahoo.com> wrote:

Question about DoCmd.PrintOut in A97.

I have a form on which all the controls are unbound. There is a large
textbox that the user can type stuff in and a couple labels. I am trying
to code a Print button to simply print out the form.

Problem is, DoCmd.PrintOut only produces a blank page. (Actually once in
testing, it printed the form module's code, but not the form.)

In another app I am working on, PrintOut successfully prints the form
and data. The difference, or at least the obvious difference to me, is
that in the other app the form's controls are data-bound.

Does this seem like a limitation of the PrintOut method? I have not seen
any indication of this in the help file, but wondered if anyone else has
had the same experience.

Thanks for any suggestions.

I am posting another question separately about a potential work-around
using a report to take care of the printing.

This is an awesome group, BTW!

Forms are for viewing, Reports are for printing.
Create a report which displays the same data as your form. Use your print button to print the report for the selected
record.

DoCmd.OpenReport "rptMyReport",,,"(MyIDField)=" & Me.MyIDField


Thanks for that, Wayne.

In my question concerning forms (<ne********************@giganews.com>)
I am able to do that much, but I was hoping to do some formatting on the
fly.

I was puzzled about my ability to print one form but not the other.
--
Smartin
Nov 13 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.