Clipper app freezing in win2000 1

[patxi]

I have an intermittent problem with clipper applications that freeze when writing to .dbf databases, leaving a half written record or blank record. It didn't happen to start with when we moved to windows 2000, now it's happening all the time. Any ideas?

 

[EzLogic]

Have you checked for DBF Corruptions/Index Corruption?

do you have full permission? what is your Lan setting? type of network.

Sometimes that could be hardware problem that's causing these strange results.

Ali Koumaiha
TeknoSoft Inc
Farmington Hills, Michigan

 

[Bozz]

Can we have a bit more information please. What exactly does "when we moved to Windows 2000" mean. If 2000 server is involved there are Opportunistic Locking issues that need to be addressed.

It's unlikely to be permissions, you either have them or don't, that wouldn't be intermittent. It could be a LAN problem, sillier things have happened.

Ian Boys
DTE Systems Ltd

 

[patxi]

Problem is running (some) Clipper 5.2 apps in Windows 2000 with Pentium 4 processors @ 2.5GHz, data is on Novell server. Previously was running on DOS and Win 98. Have read other threads about Pentium 4 problems and reducing CPU usage by using nanfor.obj but so far no success.

 

[circes9]

check the CPU utilization when your Clipper app is running, when it's locked up, etc. If near 100%, then you need to slow the KB sampling down. If that's the case, there are solutions throughout this site. I use the DPAKBD.Com routinely to handle this.

 

[patxi]

I reduced the CPU utilization to 30% and it seems to freeze when running a Printsend (clipper tools) command.