*.adm are Main Dictionaries - you should supply the ones you want your client to start with - by default (and this is all configurable), Addict looks for American.adm in the same directory as the Application. All the Dictionaries on our Dictionary Page, http://www.addictive-software.com/dl-dictionaries.htm are currently Addict 3 and Addict 4 compatible. Dictionaries built with our new Dictionary Wizard are Unicode based and thus are for use with Addict 4 Applications only. An Addict Application can have multiple Main Dictionaries.

*.adu are User (or Custom Dictionaries) - these store the not only words for spell checking, but also Auto Corrections and words to exclude from the dictionary (and thus make them an spelling mistake). So at runtime when you "add a word to the dictionary", it goes into the User Dictionary that you have chosen - which by default is %ConfigID%.adu - so for me that would default to Glenn.adu in the Application Directory. This of course can be changed. Autocorrect.adu is often a worthwhile item to also include in English Applications. An Addict Application can have multiple Custom Dictionaries.

ConfigFilename contains where the runtime options for Addict (the ones the end user sets if you allow them access to the Addict Setup) and you have ConfigStorage set to csFile (note that MS does recommend not using the registry these days) - and by default this is %AppDir%\Spell.cfg. If you are using this approach and you change some of the design time settings, then you should delete Spell.cfg (or whatever you named it) so that the design time settings can be seen. This file does not normally need to be shipped as it is created as needed.

SuggestionsLearningDict is the file that stores information about the Suggestions that are stored - and by default it resides at: %AppDir%\%UserName%_sp.adl (and thus for me by default it would be glenn_sp.adl in my application directory). This should not be shipped with an Application - and if you don't want your application producing this then set SuggestionsLearning to False.

Custom.dic is the Microsoft Office Custom Dictionary - Addict allows you to have Read Access to this if you wish (ie it will use it like a User Dictionary for checking spelling). This is not something you would normally ship, and is not really a part of Addict, rather if your end users are using Microsoft Office, then their Custom Dictionary may have some useful additions in it.

Example

For our my Company's (ie ESB Consultancy not Addictive Software) in-house work and work we do for local clients, I place my AddictSpell Component on a Data Module that I create prior to the Main Form, and in the OnCreate event do something akin to the following:



Where ESBAppDataFolder is the path where I want the config files and other items created by Addict and ESBAppUser is the user name I want to use in the filenames. To make Applications happy with Windows XP and above, I use a directory in the Application Data directory, rather than the Application Directory. Addict does have a "pattern" for this: %AppData%.

I set my Main Dictionaries (to Aussie and Technical) and my Custom Dictionaries at runtime.