OK.  Looks like "provider" is connection type.  Is SQL Native Client not automatically enabled on the server? How can I enable it?  or should I use something else?

The database code should fire on form load/render -- it is populating dropdown lists.  The data connections were configured as SQL Native Client -- could this be part of the problem?  Should I use a different connection type, or do I need to do something on the server to enable particular connection...

JasminThanks for the quick reply.  I removed the Task Manager endpoint using the adminui, then recreated the endpoint in Workbench and redeployed the application.  I am still getting the same error message in Workspace, but the top error in the log is now the following:I still want to think that it ...

After adding some OLEDB-bound data dropdown lists to my form, it no longer renders in Workspace.  Error is "An error occurred creating the form (task 27, form 0). (ALC-WKS-007-040)".  Do I have to do something (reader extend?) in my process to enable the form to render now that it has database-bound...