Keven,

It looks to me from the code and comments in the mmbuilder that the intention of having the SecurityDBC_Name setting and mechanism to open a specific database (which it does do) is also to open the mmcntrls table in the same database. However, calling mmbuilder.openmmcntrls() will instantiate mmcntrlsobj in the current project and use it's default database. So the the case where the security database is not the current project data base, the two pieces are not related at all.

Is this something the framework should be doing/insuring or is it the developer's responsibility to change the database keys in the mmcntrlsobj's data environment if SecurityDBC_Name points to a diffent database than the default. If thats the case, no problem. You would want to add a comment in the user manual of this requirement in this situation.

What is your take on this?

Thnaks,


Gary Pike.