The following steps may help,

https://es.infragistics.com/community/forums/f/ultimate-ui-for-wpf/44706/how-to-limit-which-columns-in-a-datatable-to-display#44706

However if you are using Master Pages it may not be possible for the WebScheduleSqlClientProvider to find the SqlDataSource control (the ID will be mangled), in which case you pass the ConnectionString to the WebScheduleSqlClientProvider directly.  The following thread and reply describes calling Connect to do that,

https://es.infragistics.com/community/forums/f/ultimate-ui-for-windows-forms/46025/ultranavigationbar-how-to-bind-with-objects#46025

That call needs to go near the start of Page_Load or someplace similarly early in the page lifecycle.

Depending on what the security settings in your connection string are, you may want to consult the SQL Server help topics in this section of the online help for explanations of using impersonation, etc.,

https://es.infragistics.com/help/aspnet/web-deploying-webschedule-controls-and-components-landing

However, I would say that if you are getting an error saying it tried to connect as "sa" then most likely it is trying to establish its default connection because it never received the connection string you're trying to give it (frequently this is because it couldn't find the SqlDataSource on the master page but it could be because the connection string arrives too late, such as after WebSchedule tries to fetch data).

HTH,

https://es.infragistics.com/samples/aspnet/schedule/full-page-sample

I believe the ASP.NET samples should be installed beneath either your My Documents\Infragistics folder in Win XP or \Users\Infragistics in Vista so you can examine the source for the WebFeatureBrowser / WebSchedule / FullPageSample.

https://es.infragistics.com/help/aspnet/webschedule-overview-of-the-stored-procedures-used-by-the-webschedule-data-providers

The name will correspond to the WebScheduleInfo ActiveResourceName property of the user whose schedule is being viewed.

The WebSchedule data model avoids having null relationships by using a "default" record with ID -999 to represent an Activity tied to an "Unassigned" resource.  Any activity not associated with a resource (or when ActiveResourceName isn't set) is associated with the Unassigned resource.

Other Resource fields like e-mail and preferences are only used by the Windows Service starter kit that sends e-mail reminder notifications.

These stored procedure updates should be straightforward to fit to your table.  The WebSchedule data model establishes a relationship from Resources to Activities by using the tie table, [ActivityResource], so some of the Activity stored procedures will need to be updated, too.

Stored procedures that are noted as being "only called by the WebSchedule data provider's administrative API" are not called during normal WebSchedule processing.  There are a few convenience methods on the data provider like DeleteResource( ) I think it is, in case you wanted to expose those functions to a superuser.  If these APIs aren't used, then stored procedures like Resource_RemByName will not be called and you don't have to worry about any DELETE operations on your Users table if you don't want them.