Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Computer Locks up attempting to print

Status
Not open for further replies.
Jul 3, 2000
20
US
My application resides on an NT4 server. One of the applications is used exclusively by one workstation. The program calls for a local .dbf to:
1. zap all records
2. insert a record from memory variables
3. print a report from that local table (a single record)

Every once in a while the computer will lock up attempting to print the report displaying the printer window but stopping at that point. I know that the data is added correctly into the table and the next step of the program calls for the printing (Report form METRO to printer noconsole). Swapping computers, printing locally vs. off the network, etc. have been tried. Again, it only happens occassionally. The one benefit to troubleshoot is that it will lock up on the same items again and again. I cannot recreate the fault on my computer using local data (everything works normally)

Any ideas what I can try to isolate the problem. Please!!!
 
Although it is not solution, you may try
zap
appe blank
gath memvar
FLUSH
go top
report...
If case no success, try add close and open table or wait
to create delay between file operation and reporting...
Tesar
 
The fact that you have no problems locally, but you do when the files are on the network, obviously points the direction of research. Check to make sure your NICs, cables, hubs, switches, routers, etc. are all working properly (you may need the help of your network adminstrator and a hardware line analyser for this). Note: I've seen a similar problem, when two systems were set up with the same TCP/IP address, but one was a laptop that was only connected part of the time!

Next, check for updates on the network clients and make sure they are configured properly. Delete any unused protocols, so the network traffic is cleaner.

Finally, I'd check into the server's setup - especially concerning Opportunistic Locking - there are a couple MS Knowledge Base articles on this.

Rick
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top