I am new to Mere Mortals .NET, as well as to .NET for that matter.

I have an issue with setting up MM .NET security control IDs using the design-mode builder. It appears to me that the fix would be complicated (compared to populating the control ID values and descriptions manually).

I am currently testing the use of MM with modified column names in the security tables. The point of the modifications is to match a naming convention used in other tables. For instance, the "SecurityPK" column is now called "sec_secid."

Following the MM help file, I modified the column names (in SQL Server), subclassed the security business objects in order to reassign the column name properties, and subclassed the factory class in order to instantiate the subclassed security objects.

This setup works when the application is running.

However, in design mode, when I click on the button to call up the builder form for the "ControlID on mmMenuExtender" property, the error "Invalid column name 'SecurityPK'" is displayed.

My questions are:

1. Do I need to subclass the three classes (listed below) in order to re-enable the builder?
   
2. Is there a simpler way I can tell the builder that the security field names are changed?
   
3. Are there any other hints people could share?

It appears that at least three classes used in the builder process contain hard-coded references to base MM classes. I suspect that these classes need to be subclassed and some of the references changed to deal with the builder error. The classes and references are:

  CLASS                         MM BASE CLASS REFERENCE
  mmMenuExtender                mmControlIDTypeEditor, factory?
  mmControlIDTypeEditor         mmSecurityControlIDEditForm
  mmSecurityControlIDEditForm   mmSecurity

I am not sure about the relevancy of these references because I can not get the builder to run at all if I insert a break point and try to debug.

Thanks for consideration of this issue.