Raise the SchemaCorrectionNeed exception in the Pervasive adapter

Hi,
We have researched the problem and found out that there is no way to fix this issue on the XPO level. The Pervasive DataProvider does not return error codes, but only generates string messages which cannot be uniquely interpreted. We will try to resolve this problem on the XAF level.
Thanks,
Plato

Hello Bernard,
On the XAF level, you can add a handler to the CheckCompatibilityEvent event of the Application class and manually check/update the database structure.
The simplest way is to always update the database structure:
          static void winApplication_CheckCompatibilityEvent(object sender, CheckCompatibilityEventArgs e) {
               DatabaseUpdater dbUpdater = new DatabaseUpdater(e.ObjectSpaceProvider, e.ModulesManager, e.ApplicationName);
               dbUpdater.Update();
               e.Handled = true;
          }
With this code, any error will indicate that the structure cannot be updated for some reason.
Since Xpo cannot throw the SchemaCorrectionNeedException, the XAF will not be able to properly manage the database structure. It's impossible to write a common solution which will be appropriate for any case.
You will need to write additional code instead of the standard XAF database management if you are working with a database server that is not correctly processed by Xpo.
Thanks, Dan.