This question is locked. New answers and comments are not allowed.
Hi there,
with the "new" version of openaccess, how should i update database schema on client side?
With the classic open access, i used to use vschema, specifying the assembly, config file and so on...
But it does not seem to work for the new OA. I've read the Deployement and update consideration here, which seems to be for both versions (classic and new), and which explains that we have to use vschema, however, following the link about vschema brings your here, and it seems to handle only classic OA.
Am I right?
So now, what is the good practice for updating database schema on client side (I don't know the exact updates to apply to the db, as I don't know when the last installation was done). Can I still use vschema? Is there any other way to do that?
Thanks a lot for your answers,
Antoine.
with the "new" version of openaccess, how should i update database schema on client side?
With the classic open access, i used to use vschema, specifying the assembly, config file and so on...
But it does not seem to work for the new OA. I've read the Deployement and update consideration here, which seems to be for both versions (classic and new), and which explains that we have to use vschema, however, following the link about vschema brings your here, and it seems to handle only classic OA.
Am I right?
So now, what is the good practice for updating database schema on client side (I don't know the exact updates to apply to the db, as I don't know when the last installation was done). Can I still use vschema? Is there any other way to do that?
Thanks a lot for your answers,
Antoine.