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 / Reports / Printing / November 2004

Tip: Looking for answers? Try searching our database.

Access 2003

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tom Perot - 25 Nov 2004 02:47 GMT
I have a mdb file that was working perfectly until yesterday.

Series of events.

11/05/2004 Windows NT 4.0 server w/ Win 98 clients.
11/10/2004 Replaced Win 98 clients w/ Win XP Pro clients.  Reports were able
to be printed.
11/20/2004 Replace Win NT 4.0 server w/ Win 2003 Server.  Everything works
except none of the reports can be opened, designed or previewed now in
database.  Obviously it was something to do with the rights but the users
have full rights on the folder.

Thanks
Tom
Terry - 25 Nov 2004 05:12 GMT
Tom,

Printers ...... ?  Were they all on served from the NT
server?  Check for default printers and then check the
report page setup for specific printers.

HTH,

Terry

>-----Original Message-----
>I have a mdb file that was working perfectly until yesterday.
[quoted text clipped - 12 lines]
>Tom
>.
SA - 29 Nov 2004 11:12 GMT
Tom:

Terry's comment is spot on, however, you may find that in certain
situations, you can't open your reports in design mode to change the
printers if the original network printer that a report was set to use no
longer exists on the network.  If you can open it in design mode and then
from File - Page Set Up, reset the report to use either the default printer
or a new specific printer on the network.  If you can't get the report to
open in design mode,  then if the NT box is still around, re-add it to the
network as a BDC or member server (assuming that the printer targets are
still set up properly on that box and you don't change its computer name)
and then you should be able open the reports and then set them, as noted
above, to either user the default printer (recommended) or a new specific
printer based on the convention used by the 2003 server.
Signature

Steve Arbaugh
ACG Soft
http://ourworld.compuserve.com/homepages/attac-cg

> Tom,
>
[quoted text clipped - 27 lines]
>>Tom
>>.
Tom Perot - 30 Nov 2004 15:37 GMT
I did move the database file and workgroup administrator file to another
workstation that is not on the same domain (a NT 4.0 domain) and it works
fine.
I then moved the database file that I could open up on the other domain to
the local workstation on the W2K3 domain and it shows the same condition.  I
cannot open the reports, go into design view, etc.

On the W2K3 domain, we have locked down the machines and while they are not
having any problems using other programs, could security be an issue?  

> Tom:
>
[quoted text clipped - 41 lines]
> >>Tom
> >>.
 
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.