>>If we run it as file base, no problem. However, we have that "memory streaming output has been disabled" message when we run it under a COM. So, this is why we have to maintain a secondary application for it. We can't run it as file base.
>
>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.
>
>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?

I finally implemented a file base setup for that application. Basically, that application only handles one transaction. It's a secondary server which handles only a specific type of request. We use it for PHDBase. When running as file base, we don't have the problem. For my implementation, it turned out that this is the best approach to use.