currently we are running some application based on btrieve and vDos.
Since the first versions of w10 it works very well with btrieve for dos 5.x. After some updates from MS we got troubles depending on poor network performance to SMB-Shares. So we think about some changes to the database (client/server).
So the question is about the possibility to use dos clients (for example breqtcp) under vdos for a connection to a pervasive server version 10 and up.
Did you see a solution to solve this or have you other recommendations for this situation / configuration?
BREQTCP.EXE won’t function in vDos since it doesn’t provide for an API to low level TCP/IP communications. Normally Btrieve 5.x runs fairly quick, but all database maintenance is done at the workstations. A simple serverbased “Add/modify this record” so results in several logical (4KB) database page reads and writes, with record locking in between. If Btrieves performance dropped after Windows updates, you could have a look at the optimistic record locking mechanism. It gets disabled due to the use of a mix of SMB versions at the workstations, still some XP machines around?
Migrating Btrieve 5.x to a serverbased solution would dramatically improve the overall performance. But you then have to convert the Btrieve 5.x databases to Pervasive server. If that is a valid option, you might also first have a look at BTR2SQL (https://www.mertech.com/migrate-btrieve-to-sql). That essentially replaces the need for a Pervasive server by a SQL server, while still providing the same interface at the clients/workstations. The next vDos version will support (connect to) those (Windows) interfaces directly, transparent to the DOS application.
For further information contact me directly, it will become too specific to Btrieve/Pervasive and your situation.