>Have you applied the last service pack (SP5) for VFP 6. It should clear your problem. Also make sure your system does use good HP printer drivers. Some are notorious because of causing problems in programming languages like FoxPro.

I'm still using VFP 5 (with SP3). I'm trying to determine if this is the source of the many C5 errors that I get during normal processing. For instance my last one about 30 minutes ago:

I locked up VFP with the debugger on. (Cursor froze.) So I used the task manager to end the VFP task. To be on the safe side, I restarted my Dell Win2K computer. I started up VFP 5.0 again. I started Visual Fox Express. Bang! An immediate C5 error. So I rebooted again. This time it was ok.


>
>In general I can say that I have not experienced any speeddegration when using table operations like SQL and others using rushmore. Not even under Win2K.
>
>Ohhh.. and don't use DELETED() tags. They're often the cause of performance degration.
>
>Walter,

Paige: >I was running some test on VFP 5 vs VFP 6 because my client found that 6 was much slower when using SQL. After much testing of different versions on different machines with different environments (WIN 98, Win 2000 Prof, NT WkSt and NT Server) I concluded that the difference was: Version 6 is much slower if you don't have a DELETED() Tag in your .CDX and use Set Deleted ON. It didn't seem to make much difference in VFP 5. Hope this helps. There may be some of my questions/answers in the "search" area.

Walter, I don't use DELETED() tags and I do run with SET DELETED ON. I was alarmed by the what Paige said about VFP 6 being slower if you don't have a DELETED() tag.

If true, this just deepens the DELETED() tag mystery.

Peter