I am having two problems with JDBC / FMPro implementation that i would appreciate assistance with.

1. Does the fetchsize option on the url actually work?

when i try

Class.forName(driver).newInstance();

Connection connection = DriverManager.getConnection ("jdbc:http://localhost:591/test.fp5&fetchsize=20")

my connection has no qualms returning 1000's of records.

is there any other way to limit the amount of records returned. The FMPJDBC 1.2.jar driver Does not support limit in the select procedure.

Has anyone got any experience returning repeating Fields to JDBC.

They are initially returned as an implementation of java.sql.Array and support a command getStringArray() but from there im kinda lost,as mine throws a lot of errors in my implementation.

chris stav

Do you have to use JDBC?

It is piece of cake in CDML.

yeah im well past that stage - just finding the jdbc driver a bit quirky

past that stage???

too involved with the java (jsp / servlet / jdbc) implementation to go back now.

Is there any chance of filemaker releasing the source for the driver? If they aren't going to update or provide technical support?

I don't see any advantage in using Java and JDBC with FileMaker. Don't go back; go forward to MySQL, Lasso and such. If you want to stick with FM, use what works and that is CDML.

FMI loves to put those ODBC and JDBC on their retail box. My experience is, that they *do* repair functionality buggs only in FM products and never improve those additional "marketing" bits and pieces.

Anatoli - maybe if i explain why java - you seem interested

Filemaker is being used for largeish (8*50000) records onsite. This has been working well.

However offsite to handle large numbers of clients with requests for the data we need to publish the results. The number of clients referring is around 10,000. Each client needs a login and password to access the records they individually referred, and only those. This is sensitive data and it needs to be secured.

So each of the 10,000 clients referring needs a web login and password. Thus using the filemaker pro access privelliges would not allow adding 10,000 passwords. Also filemaker 5 (which is what we are using) does not allow record level access restrictions?

So I set up a database in filemaker of the clients which contains there loginname, password, and their unique id. Then as they hit the login jsp page the servlet checks the login, and as they navigate and search to find the correct record (displayed as a jsp file), the servlet uses a session to track their access level and only show the records they have access to.

hide processing / details of data from end user.

jsp / servlets provide web implementation with server side processing.

Apache is free runs from *nix.

You dont need to purchase FMUnlimited to host for many requests / concurrent users.

Can easily implement a connection pool to greatly speed up the login / access times.

Trust apache more than FM web servers.

plus i like java

- but i still need an answer to my questions about the driver.

I've build similar login system just in FM and CDML. No big deal.

RE: You dont need to purchase FMUnlimited to host for many requests / concurrent users.

In that case you are not using FM software in accordance with their license agreement if it is >= FM 5.

chrisonmaui said:

Class.forName(driver).newInstance();

Connection connection = DriverManager.getConnection ("jdbc:http://localhost:591/test.fp5&fetchsize=20")

I think that you have an error in your url

It must be jdbc:http://localhost:591/test.fp5/properties?fetchsize=20

For repeating field you can check that

int profondeur = 0;

Vector Tableaulie = new Vector();

com.fmi.jdbc.Array MonTableau = (com.fmi.jdbc.Array) curseur.getObject(a);

String[] DonneesLies = MonTableau .getStringArray();

String[] fieldData = MonTableau.getStringArray();

profondeur = fieldData.length;

for (int j = 0; j < fieldData.length; j++) {

Tableaulie.addElement(fieldData[j]);

}