This app seems to make a lot of assumptions (!!!) about record
position. I noticed this a lot 20 years ago too. Not sure how old this
code is but I thought I saw something that said early 2000s?
On 10/2/2019 2:41 PM, Frank Cazabon wrote:
Yes, it fails if you are at EOF in the currently selected table, if I
recall correctly.
Frank.
Frank Cazabon
On 02/10/2019 02:14 PM, MB Software Solutions, LLC wrote:
We've seen this before (and I did it 2 decades ago): REPLACE
MyTable.MyField with SomeOtherTable.SomeField
The implication is that "replace the MyField value in the MyTable
table." But if one doesn't use the IN clause, will there ever be any
chance that the update to MyTable.MyField would fail?
tia,
--Mike
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
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/[email protected]
** 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.
