Hi Viktor,
IMO, it is a bug in Clipper - It should throw a runtime error - IOW,
the app thinks it wrote data but the data was never written (ie. was
lost) and therefore, that's a bug!
I see no practical reason why someone would want to do this AND I can
see that a developer would want to know that it is happening.
Regards,
Randy.
At 05:29 PM 7/7/2008, you wrote:
Hi Randy and all,
I'd vote to make Harbour Clipper compatible, unless
we have a strong reason against this practice (like
the behaviour in Clipper is inconsistent or erroneous).
Brgds,
Viktor
On 2008.07.07., at 21:02, Randy Portnoff wrote:
Hi all,
When at EOF() and attempt to replace a field, get runtime error as
"Variable does not exist" - This is better than Clipper which does
not throw an error at all, but I think a more meaningful error
message should be used like: "Attempt to update record while at EOF".
Regards,
Randy.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
