>So how can I subclass your security model and add in a new parameter for company ID as part of the userid.

We've anticipated that developers would want to extend/enhance this, so we've surfaced field names, and SQL commands so you can change these as needed.

You should create subclasses of all the security business objects (see the MM .NET Dev Guide for a list of these), and override the appropriate methods/properties. There are examples of how to do this in the Dev Guide. It's probably easiest if you look at the source code.

After creating your subclasses, you need to override the corresponding factory methods in your application-level Factory class. For example:

public class Factory : OakLeaf.MM.Main.Windows.Forms.mmFactoryDesktop
{
	public override mmSecurityManager CreateSecurityManager()
	{
		return new MySecurityManager();
	}
}

>By me altering the security table will this hamper me for future updates?

No, the table structure is extensible. You can add whatever fields you want, as long as the basic fields MM .NET expects are there (although you CAN change the table name, field names, and data types.

Regards,