>
> This changed in 2.5, because Embedded is based on the new architecture
> SuperClassic in 2.5, which doesn't hold an exclusive lock on the
> database file. This means, that several Embedded processes or regular
> Classic/SuperClassic server can connect to the same database file.
>

Yes, and I have to find the way to avoid that shared situation, source of some problems.

For example, I have a customer that did a backup (with a copy) while the applications where using the database. If then I try to use that file the embedded server crashes after connecting.

I found other case in where the customer overrided the database while the application was running, causing problems too.

I think it is needed a way to avoid sharing while the application is using the database.

Felipe.