solution import with read-only database

Classic Servoy
1

Hi there,

i have a servoy solution which interacts with different database servers
like DBF (Visual FoxPro), Postgres and MSSQL.
One of them is a remote read-only MS SQL database.
That database consists of one read-only table and some views.

When i export the solution everything works fine, but when i try to
import it on out application server i get the following (german) error message:
[error] com.microsoft.sqlserver.jdbc.SQLServerException: Die CREATE TABLE-Berechtigung wurde in der ‘DATABASENAME’-Datenbank verweigert.

My Questions are:
Why does Servoy try to make changes within an existing database?
Why isn’t it possible to import a solution for read-only databases?

Greetings,

Holger

2

somehow servoy sees changes and want to apply them
but you can turn that off there is an option "Allow data model (database) changes "

3

jcompagner:
somehow servoy sees changes and want to apply them
but you can turn that off there is an option "Allow data model (database) changes "

Hi Johan,

i already tried that before but then i got this error message:
[error] Data model change needed: server - DATABASENAME table -TABLENAME but is not allowed from import preferences.

4

briese-it:

jcompagner:
somehow servoy sees changes and want to apply them
but you can turn that off there is an option "Allow data model (database) changes "

Hi Johan,

i already tried that before but then i got this error message:
[error] Data model change needed: server - DATABASENAME table -TABLENAME but is not allowed from import preferences.

This error means that based on export information Servoy needs to change something in table TABLENAME from server DATABASENAME but is not allowed to do it. If no column name is present in this error message either table itself is missing or has missing database sequences.

5

Your’re so right!
The remote table is not existing anymore!

Since Servoy tried to make changes it’s gone.
I’ll contact the database admin of the foreign host to check that.

Is it possible that a MSSQL table is blocked by a security rule when somebody tries to write to that table…?