Page History

...

As it is common practice to have a development area and a production area, we will only mention the fact that it is important to have a good separation between your development area and your production area in order not to overwrite a released knowledge base with a development version. In Quaestor you are able to work with personal profiles (please read about startup behavior for some specific start up behavior and default setting issues). These profiles enable a knowledge engineer to efficiently work on different knowledge bases in different area’s requiring different Quaestor directory different Quaestor directory settings by switch between these profiles.

...

However, please realize that that Quaestor will that Quaestor will use the file name to associate a project file to the accompanying knowledge base. Therefore, changing file names between versions of knowledge bases is a good approach for major releases (in which it might make sense to break the association between an existing project file and this new knowledge base), but for minor releases this is not convenient.

...

After opening a knowledge base, in the “About Quaestor” window Quaestor and window Quaestor and knowledge base version information can be found.

You will find information on your current Quaestor version current Quaestor version (see http://qnowledge.nl/pub/version number convention.htm), your license information and user level.

...

2.4 General remark

Please note that Quaestor will that Quaestor will automatically store the following information as part of a solution:

...