Record locking

[Mike Schwartz-PC Support & Services]

> In other words, regarding programming code, there is (or
> should never be) any such thing as "timing problems".  In fact, I don't
> know
> what "timing problems" means in the way you're using it.

	Well, when the hardware doesn't respond in the way the software
expects it to, I guess you could call that a "timimg problem."  

	For example, on some of the Xenix versions when we used to do floppy
disk backups, the software was prompting the users to insert the next disk,
but users were pulling the diskettes out before the disk writes had
completed.  I would call this a hardware/software timing problem.  

	The other two things problems we've been discussing (records still
showing up as being locked to other users even though we have issued a WRITE
command and the inability to run multiple *report lines in a Windows batch
file) are two such hardware timing errors that we have simply learned to
program around.

	If I thought there was any reasonable way that fPtech could program
around such hardware speed limitations on a few specific computers or on a
few versions of Windows, I would certainly submit all this stuff as a bug,
even if I had to rig up a machine that demonstrates the problem and send it
to him to play with... 

	Then again, we all have better things to do with our time than to
try and troubleshoot problems that we can easily work around, especially
where answers have been posted to this list on these problems several times.

Thanks,

Mike Schwartz