Having problems getting started

I am trying to learn enough about Servoy to determine if it is a suitable tool to replace FileMaker Pro and have been following ClickWare’s tutorial for converting FMP solutions to Servoy solutions. My problem begins when I attempt to link Servoy to a newly created database file. I create a new file using SyBaseCentral, then add a line to Servoy’s sybase.config file. When I start Servoy, I get this error:

Can’t connect to the repository server specified in the application preferences.
java.sql.SQLException: JZ006: Caught IOException:
java.net.ConnectException: Connection refused

When I look in the sybase_log.txt file I see this:

E. 08/03 07:27:24. Database cannot be started – server must be upgraded to start “/Applications/Servoy/database/contact_mgmt.db” (capability 32 missing).

Is this a limitation of the trial version? I find posts here from people having similar problems, but the replies end without any useful resolutions. Here is all my version info and what I have tried so far:
Platform: Mac OSX v10.3.4 AND Windows 2000 (both with Java 1.4.2)
Servoy v2.0.4 AND 2.1b5
SQL iAnywhere9 v9.0.1.1753 (Mac), v9.0.1.1862 (Win2k)
I have made sure that everything is spelled correctly. I have followed the instruction on creating a new database file with SybaseCentral to the letter and have verified that the username and password for the new file is the default value of DBA and SQL. I have made sure there is a carraige return after the last line in the sybase.config and have tried saving sybase.config as both a Unicode Text file and a Text-Only file. On the Mac, the preference for the startup launcher is sybase_db/dbsrv9|@sybase_db/sybase.config#DYLD_LIBRARY_PATH=sybase_db and on the PC is sybase_db/dbsrv9|@sybase_db/sybase.config. I also tried replacing Servoy’s versions of dbeng9, dbinit, dbserv and dbstop with the (apparently) newer versions from the SQL Anywhere9 install.
Let me know if there is any other info required. Thanks in advance.
Steve

Firstly have you made sure that you have the current and correct java drivers for the database you are using and that they are installed in the drivers directory and then referenced in the named connection you set up?

Secondly it would probably be much easier if you simply created the tables you want directly from within Servoy.

Hope this helps.

rochard:
Firstly have you made sure that you have the current and correct java drivers for the database you are using and that they are installed in the drivers directory and then referenced in the named connection you set up?

Secondly it would probably be much easier if you simply created the tables you want directly from within Servoy.

Hope this helps.

Thanks for the reply Michael, but it does not help. Your suggestions apply to the procedure for linking Servoy to a new database, and I can’t get that far due to the error I am getting on startup.

The solution for the issue you mention (capability 32 missing) is caused by the fact that iAnywhere offers 9.0.1 for download on their website while Servoy ships with 9.0.0 at the moment. Here’s how you can get around this:

http://forum.servoy.com/viewtopic.php?p=11570#11570

jaleman:
The solution for the issue you mention (capability 32 missing) is caused by the fact that iAnywhere offers 9.0.1 for download on their website while Servoy ships with 9.0.0 at the moment.

Thank you Jan. That seems to have done the trick. One thing I had to change that was not included in the link’s instructions was, on the Mac, under Preferences>Designer, I had to change the entry for Startup launcher from “sybase_db/dbsrv9|@sybase_db/sybase.config#DYLD_LIBRARY_PATH=sybase_db” to just “sybase_db/dbsrv9|@sybase_db/sybase.config”. The one file that was in the sybase_db folder that did not have a match in the SQLAnywhere9 suite was libunic.dylib but everything seems to be working fine now. I was on the right track when I replaced the dbeng9, dbinit, dbserv and dbstop files, and just didn’t go far enough. Thanks for the help and you can look forward to more desparate posts from me in the future as I dive deeper into this great tool.
Steve Portnoy