StelsDBF - Persistent Connection Problem

Classic Servoy
1

Servoy 4.1.3
Windows Vista

We purchased the StelsDBF driver (dbfdriver.jar) in order to access Visual FoxPro legacy tables via Servoy. We put the ‘dbfdriver.jar’ file into the following folder:

\Servoy\application_server\drivers

In Servoy Developer, we created a new server connection as follows:

Server Name: arm_data_vfp
URL: jdbc:jstels:dbf:c:/arm5
Driver: jstels.jdbc.dbf.DBFDriver

Every time we launch Developer, the Eclipse Solution Explorer pane shows ‘arm_data_vfp’ under the Database Servers with a failed connection icon (red circle with a white ‘x’ in it). If we run the Smart Client at this point, we get the following error:

Cannot show form data

com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: Server arm_data_vfp not found Server arm_data_vfp not found

To get things to work, we have to right-click on ‘arm_data_vfp’ under Database Servers and click on ‘Enable/Disable Server’ (disable). Then, we have to right-click on ‘arm_data_vfp’ and click on ‘Enable/Disable Server’ a second time (enable) to get rid of the failed connection icon, at which point the connection to the database is established. Everthing works fine until Developer is restarted, and we have to repeat the disable/enable process.

How do we make the database connection persist between invocations of the Developer? Any advice appreciated.

Thanks!

2

Are you sure the database is running before starting developer? since failed connections only happen/show after at least 5 connect tries

3

Well, yes the Sybase SQL server is running, and Developer/Eclipse connects to those tables automatically. Visual FoxPro does not employ a database engine and uses free-standing tables (DBF files) that are immediately available when Developer/Eclipse starts, yet the connection does not seem to get established.

Putting the ‘dbfdriver.jar’ file in the ‘\Servoy\application_server\drivers’ folder is sufficient? Do we need to add it to a class definition somewhere to get Developer/Eclipse to recognize it at start up? Or, is there a setting in preferences that we missed?

Thanks!

4

Sounds like a driver issue to me. I think it’s a good idea to give the HXTT driver a try, we have good experience with that.