>Frank,
>
>>I have had no luck with using mmuserManager.
>>
>>I have had a bit more luck with mmAppBase.UsrMgr. Here is the code to validate the values entered and change the password that I have come up with:
>
>Actually, when I talked about using mmUserManager, I actually meant exactly what you're doing--using the existing instance of mmUserManager found in mmAppBase.UserMgr.
>
>I'm not sure why the UserMgr.UserID is empty after you save it--possibly there is code somewhere in the app that is clearing it out? For now you can try re-retrieving the current user record, or you can set a breakpoint and find out at what point the user id is getting cleared.
>
>Ultimately, I also recommend that you move the code that performs checks on the password out of your user interface and into a business object. You can subclass the mmUserManager class to create your own customized subclass and then change your app's factory to instantiate your custom class instead.
>
>All the best!

Thanks Kevin,

I now what you said should make sense to me, the words sound familiar, but I haven't quite understood what to do. I'll fudge around a bit and see what I can come up with.