"Ben" <an*******@discussions.microsoft.com> wrote in message
news:5D**********************************@microsof t.com...
----- John Saunders wrote: -----
"Ben" <an*******@discussions.microsoft.com> wrote in message
news:4B**********************************@microsof t.com... > Thanks for the reply >> I tried the control in a repeater with a single field, and it
still doesn't work. The database value is correctly sent to the control
but the attribute doesn't keep his value when the page_load is called. I
put a breakpoint in the set property of the attribute and the correct value
from the database was there, then I put a breakpoint in the page_load
where the attribute is used and it has become an empty string. Note that all
of the other attributes still correct. I drop all the javascript used in
my form but I cannot do the same with the javascript created by my control,
because it is the main function of the control, to facilitate the use of the
overlib javascript function. I assume that my script is fine because the
control work well in any other case. >> That's about it, here's some sample of the code used, maybe it'll
help >> Thanks for your time
>> Here's how I declare the control in the repeater
><asp:repeater id="Rep1"
runat"server"><ItemTemplate><UserControl:MyUserCon trol id="RO"
URLText="info" TitleBox="Details" TextBoxMouseOver='<%#
DataBinder.Eval(Container.DataItem, "EmployeName") %>'
runat="server"></UserControl:MyUserControl></ItemTemplate></asp:repeater >
Does the same thing happen if you use an asp:Label instead of your
user control?
--
John Saunders
johnwsaundersiii at hotmail
No, all the other web controls works fine; Even in my datagrid, all the
other web controls in the rows were fine
If all other controls, for instance Label or TextBox controls work, then the
problem has nothing to do with the databinding expressions. Instead, it has
to do with how your control deals with its property settings.
You should review the Control Execution Lifecycle
(
http://msdn.microsoft.com/library/de...-us/cpguide/ht
ml/cpconcontrolexecutionlifecycle.asp?frame=true). Briefly, in the INIT
phase, the control is instantiated and any properties with constant values
are set to those values. By the LOAD phase, all controls are meant to be
part of their parent's Controls collection. In the DataBind phase,
properties with a databinding expression are set.
For each databinding expression you have in the HTML source, ASP.NET creates
an event handler for the control's DataBind event. That handler sets the
properties to the specified values.
Later, in the RENDER phase, the control is asked to render itself, using the
property values.
You may want to turn on page tracing. Additionally, I've found it extremely
useful to override all the interesting methods on my controls and add
Page.Trace calls to them. This way, I can see what's going in in great
detail. I have gone as far as to create a base class for my controls and to
put these trace calls in the base class.
I suspect you'll find that the databinding is working, but that something
then resets the property to the wrong value. At any rate, it may be time for
an instrumentation run!
--
John Saunders
johnwsaundersiii at hotmail
