I created a new database w/ 3 tables running under Sybase engine 9.0.1 with Sybase Central from the 9.0.2 installer. I then created a new Servoy db server to connect the new database and used it for a new solution.
One of the three tables did not show up in data providers so I re-did the database and named connection and now a different table isn’t showing up in dataproviders.
When I try to create the “missing” table via Servoy, it gives an error about the table already existing (which of course, it does).
Anyone know why certain tables are not visible to Servoy? (I’ve checked permissions, restarted, redone, etc.)
Servoy Developer
Version R2 2.2.1-build 333
Java version 1.5.0_02-36 (Mac OS X)
Sybase ASA 9 - 9.0.0.1120
Hi JDW,
I am suddenly getting a similar issue here.
Having added new table(s) to an existing solution via define dataproviders dialogue I quit completely from Servoy Developer app then relaunch it and open the solution and the new table does not appear in dataproviders list…but is in Sybase !
This does seem to be localised to a specific database though as I have tested with another database within ASA and that one seems to be fine.
There seems to be no reason for this and it suddenly started happening on this one database two days ago !
Servoy Developer
Version R2 2.2.1-build 333
Java version 1.5.0_02-36 (Mac OS X)
Sybase ASA 9 - 9.0.0.1120
OK here’s what I did regarding the missing table(s) problem:
Exported problem solution, deleted it from repository, removed server connection
Quit Servoy, killed dbsrv9 process
Deleted problem database.db file
Amended sybase config file to delete database.db reference
Cold reboot of PowerBook
Recreated new database using Sybase Central
Added database into sybase config file
Launched Servoy
Added server connection to database.db
imported solution
The same problem persists with that imported solution - new tables do not persist after quit and launch of Servoy !
Did also create a brand new test.db add a solution and then add table through define dataproviders and this worked without displaying the same issues !
Is it fair to say that there could be a problem with the data held in the repository for that erroring solution and that this could be causing the solution specific problems ??
i.e. the problem had been exported and then imported !?!?
But, why would it suddenly go wrong with a single database over the last couple of days when it has been working happily on all the others up until then ?
And why is it OK on a new database which was created AFTER the one which is erroring ?
But, why would it suddenly go wrong with a single database over the last couple of days when it has been working happily on all the others up until then ?
And why is it OK on a new database which was created AFTER the one which is erroring ?
Cheers
Harry
I don’t remember the exact details of the problem. I do know it works well in 9.0.1. Upgrade all your db’s and you shall be fine. Upgrading shouldnt cause any problems. If they do you can always file a case with support@servoy.com