Hi Kevin,

I sent you this via private email with a picture, but for documenting here.
>
>>The issue seems to be specific to the security portion of mm only. My pages are accessing the data just fine thus far. Although I havn't tried adding, changing, or deleting any records because I can't login to do so. I havn't yet tried to turn off security on those pages to see if I can add, change, delete. I may do that next.
>
>Have you specified a SecurityDatabaseKey in your web.config file? If so, is it pointing to your VistaDB database? At the point where you are checking security, MM .NET framework-level business objects are doing the work behind the scenes--but they *do* use the same technique for determining which data access class to use. In your case it sounds like they are trying to use a SQL Server data access class instead.
>
>If you have set a SecurityDatabaseKey and still can't get it to work, I recommend setting a breakpoint on the line of code in your user login form and stepping through to see what it's doing to determine your data access class.
>

When supporting VistaDB we are overriding the CreateDataAccessObject method in our aBusinessObject. This works for our own business objects but does not handle the business objects created for security. When the security business objects are created since it comes in as "vistadb" and there isn't a switch for that, it runs the default and creates a SQL Server dataAccessObject.

Should we handle this locally by overriding our create database objects for all the security objects, or can you add a switch for this in the framework?
Thanks for all the help
Tim