>Tore,
>For an additional explanation; there are some projects which include only few tables-less
>then 10, with number of records that are measured in thousands. Changes are not frequent.
>Much of the efforts would be spent on building UI rather then manipulating records themselves. Once put in there will be rare neccessity for records changing. And if user's net infrastructure is not reliable then I decide to build whole app WITHOUT INDEXES !.
>
>Regards, Gojko.

One of my experiences is to always fix the problem instead of making workarounds which may or may not reduce the pain from the problem. Unless you fix the unreliable net infrastructure, you will NEVER get this to work reliably. If you lose the connection in the middle of a transaction, you will lose data and integrity.

Unless you rethink the whole project, and use a web solution or some sort of remote control software where ALL the data is located on the same server as runs the appliaction, or on two machines which are closely connected. I mean one data server, and one application server.