>Sounds positive. Thanks.
>
>How about ALocks()? Guess this is core VFP and not Sedna? Or am I overlooking a language feature with which I can already achieve this functionality? With all the black box automatisms I´d still like to know what the locks are. Or am I too old-fashioned and should rely on the engine?

The primary goal for Sedna is interoperability. We do plan to enhance IntelliSense and some features around the report system (does not relate to interoperability), but beyond that you can count on about everything else being something related to interop and not about the local VFP data-engine which we recently greatly enhanced in VFP 9.0.