Hi,

The problem has nothing to do with wiring up the event.

The code you initially provided in the other thread used a OPTGROUP and does not work with this code.

The code you just provided in the other thread uses a OPTION and does work with this code.

If you re-test this code with the OPTGROUP code you will find it does not work.

Doug

Hi,

Apparently, you have sent me down a dead end from the beginning.

You said to use a Template.

My code example in my intial posting 3 days ago had the following properties:

- LayoutSettings.AllowBatchUpdate="true"

- LayoutSettings.BatchUpdateSettings.AllowReviewChanges="true"

Now I understand you don't know how to make LayoutSettings.BatchUpdateSettings.AllowReviewChanges="true" work with Templates because it is kind of hard.

What do the developers say?

So, I try to forge ahead without the AllowReviewChanges and now AllowBatchUpdate is not working.

In the Server Side BatchUpdate Event

- there are e.PendingChanges

- WebRowChanges.RowState is Modified

But

- WebRowChanges.Data is null

What am I to do?

On top of that, the WebGrid Styles do not cascade to the DropDownList, even in your examples.  I have not figured out what the WebGrid Styles are so I can apply them to the DropDownList.

You said "Because cell template is only attached on the WebGrid and not attached to a physical database.".

So, how do we attach the template to the physical database?

Doug

Hi,

Does this effectively do the same thing?

<ISWebGrid:WebGridColumn
	Name="PriorityCellTemplate_WebGridColumn"
	Bound="False"
	Caption="PRIORITY"
	ColumnType="Template"
	Width="100px"
>
	<CellTemplate>
		<asp:DropDownList 
			ID="RefurbPriority_DropDownList" 
			runat="server"
			SelectedValue='<%# Bind("REFURB_PRIORITY") %>'
		>
			<asp:ListItem Text="ASSESS - 1" Value="1" />
			<asp:ListItem Text="ASSESS - 2" Value="2" />
			<asp:ListItem Text="ASSESS - 3" Value="3" />
			<asp:ListItem Text="DISPOSE" Value="D" />
			<asp:ListItem Text="UNDECIDED" Value="" Selected="True" />
		</ASP:DropDownList>
	</CellTemplate>
</ISWebGrid:WebGridColumn>

If so, and as with your example when the following is added, LayoutSettings.AllowBatchUpdate and BatchUpdateSettings.AllowReviewChanges does not recognize changes to the Controls in the Template.

What needs to be added?

Thanks,

Doug

Is there anything I can set on the Server Control or in Server Side Code?

Hi Glenn,

You did not answer all the questions.

1. Where does DynamicEditFormat come from?

- Do I need to manually assign something via a control property?

--- If so, even the Wizard does not do this.

- Is this created automatically?

--- If so where?  Maybe that is where the problem is

----- What if MaskInfo is not specified in the Control

2. What is v74f99?

I know it is obfuscated.  It is simple, don't search obfuscated code, not the source.

Just look search the source code, DynamicMaskValidator.js, for "DynamicEditFormat.IsValidateOnChange".  That will narrow down where the code occurs.

Then look for creates of DynamicEditFormat in all all the source.  Don't tell me no one there has a clue.

Or, give me the Source and I will do it.

3. What inhibits the user from typing alpha characters?

--- Is this an event or behavior?

4. What is ClientBehaviour.js for?

--- I see it in the IIS log but it is like it is not hooked up to the controls, hence that is why things are not formated as I type?

NEW QUESTION:

5. What code replaces the alpha characters while typing?

6. What code formats the input to currency?

7. Once you find 5. & 6., what code hooks up these events?

--- This way we can concentrate on why it is not doing it's job.

As for a Simple Project, it will not be simple

-- You have to setup up Forms & Authentication to start with.

-- It will takes me days to provide you with a Simple Project.

So while you wait for me, please answer my questions.

This problem can also be solved by working it forward with the clues we have and without waiting for it to be worked backwards with a very time consuming Scaled Down, not Simple, Project.

There appears to be a conflict with something in my Project since you have verified all assemblies are in place.