dbTalk Databases Forums  

Seven seconds to open a very simple report

comp.databases.ms-access comp.databases.ms-access


Discuss Seven seconds to open a very simple report in the comp.databases.ms-access forum.



Reply
 
Thread Tools Display Modes
  #11  
Old   
christianlott1@yahoo.com
 
Posts: n/a

Default Re: Seven seconds to open a very simple report - 03-18-2011 , 11:42 AM






That code doesn't seem to be resetting the default printer correctly
or I'm using it wrong.

Looking at:

http://allenbrowne.com/AppPrintMgtCode.html

I use this code when db is opened. :

Set Application.Printer = Application.Printers("Microsoft XPS Document
Writer")

No api or extra code module and the default printer stays the same
after the user exits the application.

Should I be surprised this hasn't been fixed since 2003 or more
surprised there aren't any others in a network printer environment
coming up against this problem regularly?


Anyway big thanks to Tony and Allen!

Another strange thing about this though - I've set up 2003 mdb
databases here too and never ran into this problem.

Reply With Quote
  #12  
Old   
ron paii
 
Posts: n/a

Default Re: Seven seconds to open a very simple report - 03-18-2011 , 12:43 PM






<christianlott1 (AT) yahoo (DOT) com> wrote

Quote:
That code doesn't seem to be resetting the default printer correctly
or I'm using it wrong.

Looking at:

http://allenbrowne.com/AppPrintMgtCode.html

I use this code when db is opened. :

Set Application.Printer = Application.Printers("Microsoft XPS Document
Writer")

No api or extra code module and the default printer stays the same
after the user exits the application.

Should I be surprised this hasn't been fixed since 2003 or more
surprised there aren't any others in a network printer environment
coming up against this problem regularly?


Anyway big thanks to Tony and Allen!

Another strange thing about this though - I've set up 2003 mdb
databases here too and never ran into this problem.

The network printer has been a Windows problem for a very long time. I
remember seeing it on Windows 98 looking at printers on a Novel 3.x server.
It was always workstation specific. Note: you may want to verify your
network connection, unstable connections can cause a timeout when
communicating with the printer.

Reply With Quote
  #13  
Old   
christianlott1@yahoo.com
 
Posts: n/a

Default Re: Seven seconds to open a very simple report - 03-18-2011 , 02:46 PM



Quote:
The network printer has been a Windows problem for a very long time. I
remember seeing it on Windows 98 looking at printers on a Novel 3.x server.
It was always workstation specific. Note: you may want to verify your
network connection, unstable connections can cause a timeout when
communicating with the printer.
This is WinXP with Novell iPrint Client v04.26.00.

I'm not a network guy, don't even have admin account on this computer.
How would I tell them their network has a problem when everyone else
can print documents? Sure, my network connection is sometimes
intolerably slow but sometimes it's fast as anything.

In other words, when I call the help desk and tell them their
workstation has a problem - will they just be able to come over, test
and repair it or will they even be able to detect it?


Thanks

Reply With Quote
  #14  
Old   
ron paii
 
Posts: n/a

Default Re: Seven seconds to open a very simple report - 03-18-2011 , 03:05 PM



<christianlott1 (AT) yahoo (DOT) com> wrote

Quote:
The network printer has been a Windows problem for a very long time. I
remember seeing it on Windows 98 looking at printers on a Novel 3.x
server.
It was always workstation specific. Note: you may want to verify your
network connection, unstable connections can cause a timeout when
communicating with the printer.

This is WinXP with Novell iPrint Client v04.26.00.

I'm not a network guy, don't even have admin account on this computer.
How would I tell them their network has a problem when everyone else
can print documents? Sure, my network connection is sometimes
intolerably slow but sometimes it's fast as anything.

In other words, when I call the help desk and tell them their
workstation has a problem - will they just be able to come over, test
and repair it or will they even be able to detect it?


Thanks

In the control panel under administrator tools, open the event viewer and
check system and application logs. If the card is bad, you should see
something (log shot) Anything else will need admin rights. You are looking
for errors on the network connection to the server. If you are not getting
corruption in you BE file, I doubt you have a network problem. It most
likely is a strange combination of settings and applications on the 1
problem workstation.

Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.