Bug 7195: Error 4257 DFERR_CANT_REFIND_RECORD triggers when refinding a record after deleting it

Product: Dataflex 18.2
Component: Runtime
Current status: Fixed/Implemented
Fixed in Build: 18.2.70.0 and component revision 18.2.70.0 on n/a in file n/a
Logged by: Dennis Piccioni on 09/22/2016
Last edited by: Dennis Piccioni on 05/31/2017
Reported by: Matthias Burkhardt
First reported in: Dataflex 18.2
Tested by: Dennis Piccioni on 09/22/2016 using build 18.2.70.0 and component build 18.2.70.0

Bug Text

The change between 18.1 and 18.2 was that request_validate would only refind parent records in 18.1. In 18.2 it will find refind both parent and child record and that's why there is a change in behavior. A request_delete sent directly to a DDO does not clear the DDO buffer after a successful delete, leaving the child DDO in an undefined state. It has its deleted record loaded and a refind generates the 4257 DFERR_CANT_REFIND_RECORD. The attached DataFlex 18.2 runtime (build 18.2.70.0) fixes this error.

Workaround

A request_delete sent directly to a DDO does not clear the DDO buffer after a successful delete, leaving the child DDO in an undefined state. It has its deleted record loaded and a refind generates the 4257 DFERR_CANT_REFIND_RECORD. The best solution is to send clear to the DDO after deleting a record from it to set the DDO back to a defined state and remove any traces of the deleted record from its buffer.

Email this Bug
Email this Bug to a Colleague
Send Feedback on this Bug to Data Access Worldwide

Web Links Related to this Article
File vdfvm18.2-build70.zip
URL=http://www.dataaccess.com/BugTracker/files/7195.vdfvm18.2-build70.zip

The information provided in Data Access BugTracker is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.