Leaving aside the environment stuff like SET EXCLUSIVE and SET MULTILOCKS, my
first guess is COUNT FOR actually moves the record pointer through every row
in the table, Whereas SELECT COUNT() is reading the header.
--
rk
-----Original Message-----
From: ProfoxTech <profoxtech-boun...@leafe.com> On Behalf Of MB Software
Solutions, LLC
Sent: Thursday, October 22, 2020 3:24 PM
To: profoxt...@leafe.com
Subject: COUNT FOR hangs on record locking, but SQL - SELECT COUNT(*) works
with no issue. Why?
VFP9SP3
Why would a COUNT FOR hang ("Attempting to lock") whereas my easy workaround is
SELECT COUNT(*) FROM SomeCursor WHERE <<yada yada yada>> ??
tia,
--Mike
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/mwhpr1001mb2144fa9e548c9fccc6a8b4cfd2...@mwhpr1001mb2144.namprd10.prod.outlook.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
