Alan McDonald wrote:

>
> If your application fools around with pointers and you go awol with your
> addressing, you could potentially march over the server's memory without
> raising an OS exception.

Yes, that is a possibility with the embedded engine, but that's also a
possibility with the classic engine which has been in production for
twenty years. As far as I know, no application has succeeded in writing
over the database engine memory carefully enough to corrupt a database
without causing any of the internal checks to fail. The internal checks
exist because the engine is designed to run in that environment.

Regards,


Ann