>Your feedback is absolutely great.
>
>I can now understand their massive market share here in France (in spite of their questionable marketing material!).

I like girls and at least they make a big effort on marketing materials :)


>It used to be a time -the 90s - when hyperfile was certainly not up to it. Up to rushmore engine perf. Great to hear about the linear improvements brought to the product line over time. In contrast of the support brought by MS to builders of integrated solutions, MS record is just appalling.

Well the 90s is a long time ago. I have been working with it for about a year and have not had even one single failure with HyperFile even though I have had to crash my app when stuck in loops or experienced other crashes during debugging etc. Our database for this app is about 25Gb spread over 300+ database and index files. I have found it very stable, much more so than VFP. I think it has built-in a lot of integrity checking. For example, files are created automatically and file structure updated automatically because the "analysis" inside the application (the database schema) checks all database either on demand or automatically.

I will add this important point: HyperFile in standard, direct access mode will be subject to the same problem as VFP in respect of the SMB2 issue. All direct file access databases will have this issue as it is a networking issue rather than a database specific issue. However, you can just as easily use HyperFile in Client / Server mode which solves the problem since the CS architecture handles network failures and retries.