>The main problems with phdBase that we found are that it a) doesn't support long field or file names and b) that it doesn't work reliable when the table is buffered in any datasession, and c) it has problems with private datasessions. You can work around this a bit by using the function that creates a hit cursor instead of including the phdBase query in the SELECT statement. If the table that is searched must be opened buffered, you can use a trigger to write the relevant fields in a free table that phdBase can use.

Our approach is to bounce all queries in a table which contains a subset of the main table. By that, we never apply any PHDBase command against the main table. Also, as our table size are big, we can't afford to run those queries against it. So, basically, an application runs alone to maintain the index. Another application respond to the searches.

>As for the problem in COM... Have you tried SET TALK OFF, SET NOTIFY OFF and SET CONSOLE OFF along with BITMAP=OFF in the Config.FPW?

We have only one line in Config.FPW. It's SET RESOURCE OFF. All other SETs are executed at the startup of the application. We don't have SET CONSOLE OFF and BITMAP=OFF. Have you found any reference in having those setups when using PHDBase? Also, is BITMAP a SET or we only execute that command as is? What does it do exactly?