Also, there is an urban legend
so his [comment] is probably an exageration
no, I've been doing this for about 20 years, and have handled support and problems for probably thousands of people by now.. I don't deal in "urban legends".. and I don't over-state reality and anecdotal history..
you made some good points elsewhere in this thread, but to dismiss expert advice in this manner is rude.. I'll be signing off now..
> It's over six months since it was revealed that Corel still did not support Paradox under Vista in WPX4...have they fixed this yet?
to be honest, it's doubtful that Corel will ever touch Paradox again.. all the people that were associated with it have been gone since 2002..
I didn't understand your "try to get full locks before you start" suggestion. Wouldn't that lead to roughly the same issues? A full lock prevents other sessions from reading and writing data (and restructuring to be complete).
totally different philosophy.. we've both discussed here the pros and cons of the SetBatch logic, which grabs exclusive control while others are in the app.. I prefer the "standard" way of attempting exclusive control.. attempt to get that control *before* beginning the process, so that conflicting access by other users isn't even possible..
the SetBatch process can be a good thing, or it can be a bad thing, depending on knowledge level and implementation.. it is a concept that should only be considered by extremely advanced developers, in very limited situations..
Posted 59 months ago
Speed Up TCursors with setBatchOn()
You can speed up a TCursor in by using update(), setBatchOn(), or copyToArray(). If you use setBatchOn(), make sure to follow it with setBatchOff() every time you use it.