Advantage Developer Zone

 
 
 

9.1 Effects of Upgrading


Please be sure to read the effects of upgrading in the help file for 9.1. There is a "breaking change" for those using proprietary locking:

"In older versions of Advantage, proprietary locking did not open files using an exclusive mode, instead it used a "deny write" open mode. While this would allow non-Advantage applications access to the data files, it could also lead to index corruption. Non-Advantage applications could still lock bytes in the files causing Advantage read and write operations to fail. For this reason the default proprietary open mode was changed. If, however, you require other non-Advantage enabled applications (such as backup software or reporting software) to open files in a shared, read-only mode, a server option is available to revert to older behavior. For details, see the Non-Exclusive Proprietary Locking configuration option."

We made the breaking change intentionally in order to prevent index corruption on existing installations. It turns out this issue has been fairly wide spread and it is quite easy to cause index corruption if opening the files with a non-Advantage process while Advantage is writing to them. We don't take "breaking changes" lightly, but all agreed that this index corruption behavior was one that the out-of-the-box configuration of Advantage should not have.

In the first 9.1 service update we will modify the config utility to include a checkbox for the new option (so end users don't have to touch the registry). If you are concerned about customers modifying the registry before we ship a new config utility, I would recommend using a .reg file so they can avoid the registry editor.

J.D. Mullin
Advantage R&D