It does to me (and it's very easy to do). I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be Forgive your enemies - it messes with their heads My blog | My articles | MoXAML PowerToys | Onyx

Ok... So, what you are initially doing is having every instance of your control share the same instance of ObservableCollection. However, you do allow the user to overwrite said instance through your property setter. That will cause you *many* problems down the road with data binding. One area where WPF crumbles hard is when you start switching around instances of objects or creating temporary objects, etc. because it depends on those being the same object to function. Now, C# doesn't have pointers, but I will use them to illustrate what I am trying to explain. 1) you create your control, your control creates an ObservableCollection() [0x1000] 2) a user of your control subscribes to [0x1000].CollectionChanges 3) a user calls your setter with a new ObservableCollection() [0x2000] Guess what happened? Everybody subscribing to the [0x1000] collection events is now broken. Everybody making changes to the [0x1000] collection is broken as well. [0x1000] is now orphaned. What you want is for each instance of your control to create its own ObservableCollection and *NEVER* let anybody change that. It is important that if you created [0x1000], that it remains [0x1000] for the lifetime of your control. Otherwise bad things will happen. Now, the read-only DP will not fulfil your just mentioned requirement of binding to collections. Fair enough. What you are trying to do here is combining TWO techniques into ONE which will cause you the problems just mentioned. If you look at the ListView or TreeView for example, you will see the proper way to lay out your control. public ObservableCollection Items // this *MUST* be read-only { get { ... } } public IEnumerable ItemsSource /// this is how people will pass in collections { get { ... } set { ... } } So what happens here is that people can add items manually to the Items collection OR use the ItemsSource to pass in collections. If you only need to allow passing in collections, use the IEnumerable ItemsSource method instead. If you want to support both, you need to add some "protection" code... i.e. don't allow use of Items if ItemsSource is not null and vice versa, etc.

I used to love Delphi but my experience with it is 7 years old now/Delphi 5 and 6/. What has changed so drastically to shift the Delphi in the dark side? The narrow specialist in the broad sense of the word is a complete idiot in the narrow sense of the word. Advertise here – minimum three posts per day are guaranteed.

Glad I was of help :)

Did I understand correctly that you're querying for branches which have a specific id? I that's correct, I think it could be something like: using(DataModel.DatabaseDataContext context = GetDatabaseContext()) { var result = from b in context.Branches where b.Id == id select b; foreach(Branch branch in result) { ... } } The need to optimize rises from a bad design.My articles[^]

How about replacing your XBAP link to a html link (with target="_blank") then in the new html page you can host the XBAP. Online Guitar Tools

Kinda hoped there would be a more specific event that I did not know about, ho well, many thanks anyway Paul

Yes you can by adding the where clause and specifying the restriction you want to apply but I'm not sure if you can limit T to only those nine types. For the constraint that you can apply have a look at this: Types of generic constraints[^] #region signature my articles #endregion

I would look at BizTalk for this if I were you. It sounds like an ideal problem for BizTalk. Deja View - the feeling that you've seen this post before.

for getting file icons you need to use shell APIs. you can use the following snippet. // define a struct for getting info from shell [StructLayout(LayoutKind.Sequential)] public struct SHFILEINFO { public IntPtr hIcon; public IntPtr iIcon; public uint dwAttributes; [MarshalAs(UnmanagedType.ByValTStr, SizeConst = 260)] public string szDisplayName; [MarshalAs(UnmanagedType.ByValTStr, SizeConst = 80)] public string szTypeName; }; // define this class for invoking shell api to get file information class Win32 { public const uint SHGFI_ICON = 0x100; public const uint SHGFI_LARGEICON = 0x0; // 'Large icon public const uint SHGFI_SMALLICON = 0x1; // 'Small icon \[DllImport("shell32.dll")\] public static extern IntPtr SHGetFileInfo(string pszPath, uint dwFileAttributes, ref SHFILEINFO psfi, uint cbSizeFileInfo, uint uFlags); } // write the following code where you want to get the selected file icon. IntPtr hImgSmall; //the handle to the system image list string fName = "c:\\getfileicon.cs"; // 'the file name to get icon from SHFILEINFO shinfo = new SHFILEINFO(); //Use this to get the small Icon hImgSmall = Win32.SHGetFileInfo(fName, 0, ref shinfo,(uint)Marshal.SizeOf(shinfo),Win32.SHGFI_ICON |Win32.SHGFI_SMALLICON); /* //Use this to get the small Icon hImgLarge = Win32.SHGetFileInfo(fName, 0, ref shinfo,(uint)Marshal.SizeOf(shinfo),Win32.SHGFI_ICON |Win32.SHGFI_LARGEICON); */ //The icon is returned in the hIcon member of the shinfo struct System.Drawing.Icon myIcon = System.Drawing.Icon.FromHandle(shinfo.hIcon); // do whatever with this icon. i.e I am adding it to an Image List. imageList1.Images.Add(myIcon); I think this code would be helpful. Saqib

If you're using VB 2003 they don't exist but there is an MS add-in that provides them. Kevin