I’m attempting to import a copy of my working Servoy 2.2.7 solution into a secondary repository for upgrade to Servoy 3.1, using MSSQL 2000 for both the repository and the solution database. Servoy 3.1 rejects the solution import on the basis that the percent fields (which are defined in SQL Server as type REAL) should be within range 0…19 and is currently set to 24. SQL Server sets REAL type fields to 24 by default and won’t let me change them. This database was built in SQL Server by a separate DBA – she’s willing to have me change them to FLOAT if required by Servoy, but it’s not required by Servoy 2.2.7 – and an associate of mine tried that and still didn’t successfully connect so I haven’t tried it yet. Suggestions?
The error is literally this: com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: The scale (24) for column ‘retention_percent’ must be within the range 0 to 19.
Hi,
You write that the table was created by the DBA before you attempted to import the solution.
In that case Servoy should not try to create the table or the column.
But the error looks like an error at creating the column.
Did you restart developer after creating the table outside servoy? Otherwise servoy developer did not know of the existence of the table/column and may try creating it.
Rob
Hi Rob – Thanks for answering, getting desperate here for an answer. No need to restart Servoy – this is a fresh install of 3.1 and the table structure is longstanding (in production use for 2.27, though not on the same install of course). Didn’t add the table or fields during the Servoy session or anything like that.
This happens to us all the time in 2.27 though, that Servoy tries to create/add tables that already exist. It mostly doesn’t bother us if we’re set to dbo privileges, but if we’re less than that it complains that it didn’t have rights to create tables that ALREADY EXIST. We don’t know why it wants to do that, but we got around it by making our Servoy user dbo. It doesn’t seem to hurt anything. But very annoying, because I have a sep DBA we’d love Servoy not to have those kinds of rights. I mentioned this at the last Servoy conference btw – I think it’s a bug really, but we discussed a feature to disallow table structure changes by Servoy while allowing the import.
This is SQL Server 2000 btw. I really need to solve this, so I appreciate your help. If I can give you ANY more info, I’ll be watching this thread closely all week to respond quickly.
ellen meserow