>1. All settings go into the same INI file !
>--> User 1 turns ShowTipos on, User 2 turns it off again ??
>--> Even worth: All form settings (position) do not on the user ??
>I can't believe this, did I oversee anything ?

This sounds like you have a shared .EXE on a network and the INI file by default resides in the same directory that the .EXE is run from. Our approach is to keep a master .EXE on the network and have a launcher that checks for a new .EXE and copies it down to each users local drive thus giving each user their own separate INI and making updates to all workstations happen automatically.

>2. The about widow does not show any information (registered User...) any more.
>It seems like switching to INI file causes the framework to through all registry possibilities away ?? That can't be true. Even when I want to use an INI file my computer still has a registry ?!?!?! And I need information from it, even if I don't want to store my settings there

It is either INI or registry not both. The decision to use INI or registry should be made up front in a MM project and normally you wouldn't switch between the two. A program could be written to transfer all the information stored in the registry for an MM application to an INI file. They both have the same structure in MM. I like the idea of having most user settings in a user file so that no matter where the user signs in they will get their settings.

HTH

Dan