I realise that this functionality is already in DBISAM 4 but I was just
wondering if there was any way of finding out what SQL has been executed
behind the scenes in DBISAM 3.30 (e.g. opening a certain table is
slow, so I'd like to see what Sql DBISAM is executing when opening the
table, so that I can start performing optimizations with a query
component instead).
Hope that makes sense.
I didn't know where to post this (in the SQL newsgroup or client
server). But I'm only concerned about speed when using this in a
client/server environment.