>My client said that for the software I was working
>on does not have a need for security, log-in, passwords
>mecahnism.
>
>But I was reading up on the security issue and understood that
>if you need such mechanism you'd better put it in the early
>stage of the project. That makes your life much easier, said the author of the VFP
>book.
>
>I got thinking. What if long after the software is delivered
>and my client would say he needed the security then. Or I can sell
>this product to other clients who needs a security on it.
>
>what's UT members' take on this? Is there any easy thing
>I can put in without actually using it or showing it
>till the need arizes?
>
>
>Any suggestion?
>
>Aiko Ichimura

As long as all of your forms and controls are based on classes, it should not be a problem. Also, when programming instances and writing code in events like refresh and init, always put a DODEFAULT(). That way, later on down the road when you do need to implement security at the framework level, all of your forms will respect the changes you made to your classes.