more improvements and fixes
Updated 16 Jun 98 for Alpha2
Reworked Database Code
The main thrust of ChemFinder 5 development was to rewrite the core database functionality. We are now using Microsoft DAO classes instead of the less-capable ODBC. New ChemFinder classes were developed to handle tables and stored queries in a uniform way. The structure-specific portions of the storage and search code were extracted into a compact, portable, documented library. Code was cleaned and tightened everywhere.
Benefits of this work include new features, tighter code, easier maintenance, better performance, more use of Microsoft code, and closer integration with the Windows environment.
Reworked Error Handling
Much of the error handling in ChemFinder 5 has been rewritten, using exceptions instead of standard function error returns. Benefits of this work include cleaner code, more consistent error presentation, and more robust error recovery.
Note: in Alpha1, resources were not built correctly and many new error messages did not appear. This problem is fixed in Alpha2.
In ChemFinder 5, you can directly convert structures to and from SMILES.
To convert a structure to SMILES:
To convert a SMILES string to a structure:
ChemFinder 5 runs only under Windows 95 and NT.
ChemFinder 5.0 supports menu extensions which also requires OLE Automation support to change ChemFinder's menus. See the ChemFinder 5.0 Menu Extension Interface and ChemFinder 5.0 Menu Automation Interface documents for description of menu extensions and how to make them availible via the menus.
If you have a functioning sound card, ChemFinder 5.0 plays little sounds on various occasions. There is a click sound when data is committed to the database (edited or added), a beep upon error, and others.
To hear the sounds:
OLE Automation Enhancements
The OLE Automation interface is changing in order to look more like a real OLE Automation interface with collections and such. See ChemOffice/SDK ChemFinder Changes for details.
To see the entire interface: