Hi All,

Thank you for assistance in advance.

I have designed a User CONTROL called DateRangeSelector to be added to several of my existing User MODULES on various pages within my portal. It is simply a dropdown box with choices "Last 3 months, Last 6 months, Last 12 months" , etc to set the start date of a SQL query.

Within the one existing MODULE that I have designed and tested this new CONTROL, it works perfectly as long as I am logged in with my SuperUser account, the one I was using during development and design.

When I login with any other account that has normal access, "Demo" for example, the new User CONTROL is not firing. Its there, I can make selection changes(its a dropdown list), but nothing fires. Other normal controls (not UserControls), like dropdown lists, work as they should.

I have placed my new user CONTROL in a folder called UserControls at the root of my DNN installation.

Why isn't my new UserCONTROL contained within my UserMODULE not working for all other users?

User Control:

<%@ Control Language="C#" AutoEventWireup="true" CodeFile="DateRangeSelector.ascx.cs" Inherits="UserControls_DateRangeSelector" %> onselectedindexchanged="ddlChoices_SelectedIndexChanged" AutoPostBack="True" onprerender="ddlChoices_SelectedIndexChanged">

All Dates
Last 3 Months
Last 6 Months
Last 12 Months
Last 18 Months
Last 24 Months
Custom...

Of course I have a proper code-behind file too for all the actions.

In Module Registration:

<%@ Control Language="C#" AutoEventWireup="true" CodeFile="RptDslvGasDetail.ascx.cs" Inherits="RptDslvGasDetail" %>
<%@ Register assembly="AjaxControlToolkit" namespace="AjaxControlToolkit" tagprefix="cc1" %>
<%@ Register assembly="System.Web.DataVisualization, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" namespace="System.Web.UI.DataVisualization.Charting" tagprefix="asp" %>
<%@ Register src="../../UserControls/DateRangeSelector.ascx" tagname="DateRangeSelector" tagprefix="uc1" %>
.......

Thank You

Elgin

While working on other parts of the project, I figured out the err of my ways.

My only mistake was not realizing that I had, when I initially designed this application, specified two different SqlDataSources for the two different levels of user that login to view this page.

And while developing this User Control, I had changed the SelectParameters of my SqlDataSource1 from "asparameter" to a proper asp:ControlParameter in order to take advantage of my new control's functionality.

I simply overlooked making the change on my SqlDataSource2 SelectParameters . Oh well, continue to live and LEARN.

Elgin

Glad that you found it!