We haven't tried with current versions of v20. The problem is the bug doesn't surface until the db is run in production, and then crashes several times per hour. 4D has so far been unable to track down the cause from stack traces and memory dumps. They want us to turn 4D's debug mode on, but that makes the db unusably slow, so we are kind of stuck.
I'm hoping one of you is in a position to help 4D figure this out.