Speed

Hi

Yes, it is possible.
It is impossible to give any advice without seeing the problem and unfortunately not all problems can be solved.

Hi Adam, Hi Sparrow,
If you've already eliminated the 'usual suspects' (calculated fields, storing images etc in the DB rather than as link files etc), the other consideration might be your actual data schema.
It's a long shot but perhaps you could look to denormalise a few things (basically reduce the number of related tables, even if it is at the expense of a bit of data redundancy and data integrity).
The problem is that it's pretty hard to test something like that other than 'trial and error' (usually more 'error' on my part ).
Maybe attach your project and see if anyone can spot something?
Regards,
Derek.

Specify how exactly the slowdown manifests itself?

1. MVDB does not create any indexes except the primary one. And if you have queries with sorting, they can work slowly. Solution: add the necessary indexing yourself.

2. Sorting when switching columns is performed on the client, and with a large number of records this can be a problem.

Hi Adam,
Just a thought - and it may not be relevant to your project - but if you're doing multiple updates (for example, processing through a grid / tree) maybe you could try using 'BeginSQLiteTransaction.....CommitSQLiteTransaction'.
I don't often use it (don't have much need) but when I have, it's made quite a difference.
Derek.