Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Forms Programming / May 2007

Tip: Looking for answers? Try searching our database.

I need help! Please MVP's, help me out

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
RobUCSD - 11 May 2007 16:11 GMT
I've been posting the below all this week and no one's been able to help me
get things working. Please help, I need to get this working by Monday am in
order to deploy my app over via citrix .

I have a command button on a form "Print Case Report" that won't print
the report. It appears to go to the printer as I can see momenentarily the
little "printing pages 1-6", but then noting prints out. It will print if I
open it in print preview and right click on it and then click on print. I
don't understand this. Another on of my reports prints just fine with the cmd
button on the form. Any help is greatly appreciated. Here's the code behind
the button.

Thanks, Rob

Private Sub cmdPrintCaseReport_Click()
On Error GoTo Err_cmdPrintCaseReport_Click

Dim stDocName As String

stDocName = "rptCaseReport"
DoCmd.OpenReport stDocName, acNormal

Exit_cmdPrintCaseReport_Click:
Exit Sub

Err_cmdPrintCaseReport_Click:
MsgBox Err.Description
Resume Exit_cmdPrintCaseReport_Click

End Sub
Damon Heron - 11 May 2007 17:42 GMT
Would acViewNormal make a difference?  I am not sure, but that is what help
says to use.

Damon

> I've been posting the below all this week and no one's been able to help
> me
[quoted text clipped - 31 lines]
>
> End Sub
RobUCSD - 11 May 2007 17:58 GMT
No, it didn't make any difference. Thanks for you response though. Do you
think the report could be corrupted and that is why it won't print?

> Would acViewNormal make a difference?  I am not sure, but that is what help
> says to use.
[quoted text clipped - 36 lines]
> >
> > End Sub
Daniel - 11 May 2007 18:17 GMT
Have you tried opening it manually and printing it?
Signature

Hope this helps,

Daniel P

> No, it didn't make any difference. Thanks for you response though. Do you
> think the report could be corrupted and that is why it won't print?
[quoted text clipped - 39 lines]
> > >
> > > End Sub
RobUCSD - 11 May 2007 18:43 GMT
Yes, as you can see from my original post I can open it in preview and print
it out using right click. It just won't print from the command button. Could
the form be corrupted?

Thanks.

> Have you tried opening it manually and printing it?
>
[quoted text clipped - 41 lines]
> > > >
> > > > End Sub
Maurice - 11 May 2007 19:04 GMT
Sorry I'm not an MVP but i'm willing to try and think here with you...

1. Have you tried copying your report and rename it to a new name and than
printing it.
2. Have you tried placing a new button on the form which just prints out
this report (al for testing purposes)
3. Are other reports printing as they should
4. Which printer is designated to the report (take a good look because you
can specify a specific printer per report) Report in design view - File
printproperties - rightclick on report for properties and look for weird
things

Let us know what you've come up with after checking the points above...

Maurice
5.

> Yes, as you can see from my original post I can open it in preview and print
> it out using right click. It just won't print from the command button. Could
[quoted text clipped - 47 lines]
> > > > >
> > > > > End Sub
RobUCSD - 11 May 2007 19:17 GMT
Thanks Maurce,

1. yes
2. yes
3. yes
4. I can't seem to find where to check for this property. I've looked in the
report properties and don't see where to designate a printer. I'm using
Access 2007, don't know if this makes a differnce. Exactly where would I find
out which printer is designated? Thanks, Rob

> Sorry I'm not an MVP but i'm willing to try and think here with you...
>
[quoted text clipped - 64 lines]
> > > > > >
> > > > > > End Sub
Maurice - 11 May 2007 19:37 GMT
Ok, we've eliminated some pointers..

It's good to hear you are using 2007 (try mentioning this in your next
posts..).
If you want to find out which printer this specific report is designated to
do the following:

Place report in design view (or layout-view for that matter..)
If correct you should see the contextal tab "Report Layout Tool"
Choose "Page Setup" and check the settings there.

ok check and i'll check some more on my machine with 2007

Maurice

> Thanks Maurce,
>
[quoted text clipped - 74 lines]
> > > > > > >
> > > > > > > End Sub
RobUCSD - 11 May 2007 19:44 GMT
The printer is set up to the default printer which is what I want.  I'm just
puzzled. Thanks for your help Maurice.  Rob

> Ok, we've eliminated some pointers..
>
[quoted text clipped - 89 lines]
> > > > > > > >
> > > > > > > > End Sub
Maurice - 11 May 2007 19:53 GMT
Ok, another bites the dust.

In print preview try exporting it to Word (in the print preview ribbon on
the right)
Does this work?

Maurice

> The printer is set up to the default printer which is what I want.  I'm just
> puzzled. Thanks for your help Maurice.  Rob
[quoted text clipped - 92 lines]
> > > > > > > > >
> > > > > > > > > End Sub
RobUCSD - 11 May 2007 20:12 GMT
Maurice, strange thing. When I try to export it from the ribbon it see's the
report by a different name and save's it as a different object in my database
(form), but when I do a save as rtf it saves it ok. ???????  Thanks for your
persistence. Rob

> Ok, another bites the dust.
>
[quoted text clipped - 100 lines]
> > > > > > > > > >
> > > > > > > > > > End Sub
RobUCSD - 11 May 2007 20:16 GMT
Wait Maurice, I have the report as Modal, when I changed it I was able to
export it as an rtf, Could the modal thing be the problem?

> Ok, another bites the dust.
>
[quoted text clipped - 100 lines]
> > > > > > > > > >
> > > > > > > > > > End Sub
Maurice - 11 May 2007 20:52 GMT
Hmm, not that I know of but in that situation I always try everything so why
not try making it modeless. It would surprise me if that's what's causing the
trouble.
But just for testing sake... have you tried the option of exporting it to a
different DB -option can be found in the same ribbon as exporting to Word.

Have you tried debugging in immediate window to see the actual name of the
report

As a final option - sorry to say but i'm running out of options.. Have you
tried making a PDF of the report and tried printing that?

Maurice

> Wait Maurice, I have the report as Modal, when I changed it I was able to
> export it as an rtf, Could the modal thing be the problem?
[quoted text clipped - 103 lines]
> > > > > > > > > > >
> > > > > > > > > > > End Sub
RobUCSD - 11 May 2007 21:21 GMT
Maurice, thanks so much for your outstanding effort. I'm just going to
rebuild the report and see what happens. Thanks again and in my opinion you
are a MVP.
Robert

> Hmm, not that I know of but in that situation I always try everything so why
> not try making it modeless. It would surprise me if that's what's causing the
[quoted text clipped - 117 lines]
> > > > > > > > > > > >
> > > > > > > > > > > > End Sub
Maurice - 12 May 2007 08:30 GMT
Rob,

No problem, can you let me know if the new report you've created is printing
as you would like it to be. That way we can suggest other people to do just
that as a final solution.

Regards, Maurice

> Maurice, thanks so much for your outstanding effort. I'm just going to
> rebuild the report and see what happens. Thanks again and in my opinion you
[quoted text clipped - 122 lines]
> > > > > > > > > > > > >
> > > > > > > > > > > > > End Sub
RobUCSD - 12 May 2007 16:47 GMT
Yes Maurice, the report is now working properly. I tried opening a new report
and copying the entire non-working report to it. That didn't work, so I tried
copying all the sub reports to the blank report and they worked, then I
copied the report header to the new report and set the data source to the
underlying query and now the report works like I want it too.

Possible corruption with the old report is the culprit I presume. Again,
thanks for all your help. Rob

> Rob,
>
[quoted text clipped - 130 lines]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > End Sub
RobUCSD - 12 May 2007 19:13 GMT
Works fine now, Thanks for everything maurice. Rob

> Rob,
>
[quoted text clipped - 130 lines]
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > End Sub
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.