The easy way to do this is to use a trick I describe here[^]. Basically, you don't show them as DataTemplates. What you do is to convert your DataTemplates into ControlTemplates, and then have a single DataTemplate that uses DataTriggers to swap templates depending on the underlying data. *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington "Mind bleach! Send me mind bleach!" - Nagy Vilmos CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

From your original post, it sounded like you wanted to add the same exact functionality to several different controls. If that was/is the case, then think about it: Its easier to write ONE attached behavior vs a bunch of MyComboBox, a MyButton, a MyCheckBox, etc controls and C&P the code. The behavior you wrote is hard coded to the ComboBox, but it doesn't have to be hard coded to any specific control type, it can be much more generic. Then you can simply attach it to any control you like. Think of something like a tooltip control. By using attached behaviors, you could attach the tooltip to any control you like. In addition, attached behaviors allow you to modify a controls' behavior without re-templating an entire parent control just to change an embedded control type. I.e. say you had a data grid and wanted to change the behavior on a ComboBox deep down in the visual tree. You'd have to re-template the entire data grid just to change a to a . In regards to your last question, there is no need to create a temporary command and use InputBindings. Just subscribe to the KeyDown message and trap the ESC key.

Ok think i have solved the issue i was having, wit the lookupnot updating the control it was on, the cause was only scalars automatically trigger a change notification, the solution was adding the following to a partial class. public partial class Charge { public Charge() { this.ActivityReference.AssociationChanged += new System.ComponentModel.CollectionChangeEventHandler(ActivityReference_AssociationChanged); } void ActivityReference\_AssociationChanged(object sender, System.ComponentModel.CollectionChangeEventArgs e) { if ((e.Action == System.ComponentModel.CollectionChangeAction.Remove)) OnPropertyChanging("Activity"); else OnPropertyChanged("Activity"); } } If any one is able to share a best practice way to make the lookup use the same ObjectContext as the Window is using that would be most helpful. I think the line below outlines the situation i am in, and the aim is for the cEntities Context = new cEntities(); from the window to be used in the lookup when popluating the ComboBox.ItemsSource. Window>Databound List View>Item Template>Lookup User Control

Don't worry about it - we all started off fearing WPF; soon the love comes. I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be My blog | My articles | MoXAML PowerToys | Onyx

The data types being indexed does not have impact on the size used to store the indexes. What you described indicates even more indexing is needed for the database table since some simple "select" queries are very slow. You may need to remove some indexes not being used by the program and add some new indexes based on the queries frequently conducted. When the needed index does not exist, "select" queries on such large tables will be very slow. I was once amazed by how much performance gains was brought by adding proper indexes when I was working on a large database table (similar to your case). So it may worth a try to get a close look at the database to find out what you need for it.

ok, i've got this all working now, i had to do something that i'm not massivly proud of, and i know its not very VB in its workings but here goes, just incase any one is in a similar situation. The issue i was having was that the reference in the structure would change to point at the newly created control, insted of pointing the class level object to point to the new control. I'm aware this is how things are designed to work, just lacks the ability to tell it how i want it working. So i wrapped the control in a class, like so. Class uscHolder Public ctrl As UserControl Public Sub New() ctrl = Nothing End Sub End Class That way the structure will not change its reference to the new object, that will always point at the class level object. That way setting the usercontrol in the wrapper class is applied every where. Thanks agian for all the pointers, once i have a problem in my mind though even if its not the solution i use in the long run it will bug me untill i can think up a solution. When coding nothing should ever be impossible is a mindset i'm stuck with.

Just send a web service request to the server with your parameters for the word/excel file, have the server create the file. The web request can bring back a temporary URL with the desired file that you would link to in a popup window.

It looks like the CurrencyManager and binding objects are what you're looking for: http://en.csharp-online.net/DataViews_and_Data_Binding%E2%80%94CurrencyManager_and_BindingContext[^] http://msdn.microsoft.com/en-us/library/system.windows.forms.currencymanager.aspx[^] These will ensure that if the two views are bound to the data through the same binding contect and currency manager, that a selection against one view will cause the same selections on the other. modified on Monday, December 8, 2008 12:05 PM

The Read method doesn't have to read all data that you request. It returns the number of bytes actually read, so you have to loop until you have filled the buffer or until the method returns zero. Dim offset As Integer = 0 Dim bytesRead As Integer Do bytesRead = stream.Read(buffer, offset, buffer.Length - offset) offset += bytesRead Loop Until bytesRead = 0 Or offset = buffer.Length Return offset Experience is the sum of all the mistakes you have done.

Your right in saying only one level is needed, the inner loop was only added after i initially had problems. This works fine for all controls on the controlList passed in, but when it calls its self when it finds a control with child controls i get an error casting from the child controls to a control list even though they appear to be of the same type. Any ideas on why the cast fails would be appreciated.

Ed Hill _5_ wrote: many thanks You're most welcome Regards J O H N :rose: "Even eagles need a push." David McNally