>Hi Victor,
>
>Yes, from what I have able to determine thus far, it does seem as if MySQL is performing a query on the backend. With that in mind I tried setting the the view's parameter to a value that would quickly hit the index and result in no matching records, however that did change anything so while a select seems to be occurring it appears that the parameter of the view has nothing to do with it.
>
>I had considered not destroying the DBC that holds the views, when the user exits the app, so that I only pay the penalty for the delay creating those views once, but that leaves behind a container file that can be examined to reveal user logins and passwords etc.
>
>It would seem that there must be a solution to this, somewhere......??????

You can keep user logins elsewhere... i.e. instead of opening the views with a connection, open them with a handle (in connection clause - not too intuitive, but the better for security :), and acquire the handle from somewhere inside your exe.