The FM 11 driver should be comparable in speed to the FM 10 driver.
Could you enable the ODBC tracing log and reproduce the problem? It would be useful to be able to determine where it is hanging up.
Also, the driver has the ability to log long queries. If you enable that for your DSN and set a threshold of, say .5 second, you might be able to see if any particular query is taking up all the time.
When you specify the paths for the log files, make sure you specify a path that is writable by the user account owning the web server process - otherwise the log won't get populated.
I tried the log long queries option and it created a blank log file and never put anything in it. Upon researching it further I found other people who said the option does not work on Windows 7 or Windows Server 2008.
We have returned to FileMaker 10 for now, but we'll hopefully get a test server up soon that we can try other logging options on.
I face similar problem with Jdbc.
With FMSA10, it works great.
With FMSA11, it is very slow.
The sequelink jdbc driver seems to be faster than the new jdbc driver.
Is it possible to use the sequelink driver with the FMSA11 ?
And since I installed V11, I face too the following error when using Jdbc: "address already in use: connect"
Any ideas ?
> I face too the following error when using Jdbc: "address already in use: connect"
(bug in my code)