TheComputerMan wrote: I simply re-compiled version 2.5 to target the .NET 4.0 framework. Since the problem does not exist in 2.5 I am happy Whehe, nice pragmatic approach :-D Well done :thumbsup:

Yes, thats equivalent. I just prefer the readability of the CTE (which is merely an opinion) plus that you can refer to a CTE in more than one place. "The ones who care enough to do it right care too much to compromise." Matthew Faithfull

Yes, it applies to Form class too. As far as the Runtime is concerned, Form is just a Type, it gets no special treatment from the Runtime.

Pretty much what I was thinking. Thanks for you help.

TheComputerMan wrote: Sorry what assumption am I making? It would of course be your assumption, so there is no way for me to know what it is. You have an impossible situation. Since computers are deterministic that means that you made an assumption which is wrong. You can't find assumptions by looking at code (although code might have been written with an assumption in mind.)

We live and learn and live to learn another day! Thanks again. Once I have uncrossed by eyes I will see if I can assimilate any of that and become 1 of 10^666 Neat PDF that on Wolfram. Devilishly cunning stuff!

Thanks Dave Yes I am beginning to wonder. I have to go on what he tells me, but of course I cannot confirm. I will call this a day here as I am sure the problem lies with the user. Many thank for your assistance.

I know the issue has been resolved; but, I just read the post. Here's another take on a solution. This code uses the Date Wizard class library to come up with the converted date variable. (Click here for the article on the Date Wizard.) Imports _2gs_datewizard '** Split source string on spaces (source string is in Textbox1) Dim ss() As String ss = TextBox1.Text.Split(" ") '** Convert the month in ss(1) from a name to a number Select Case ss(1).Substring(0, 3).ToLower Case "jan" : ss(1) = "1" Case "feb" : ss(1) = "2" Case "mar" : ss(1) = "3" Case "apr" : ss(1) = "4" Case "may" : ss(1) = "5" Case "jun" : ss(1) = "6" Case "jul" : ss(1) = "7" Case "aug" : ss(1) = "8" Case "sep" : ss(1) = "9" Case "oct" : ss(1) = "10" Case "nov" : ss(1) = "11" Case "dec" : ss(1) = "12" End Select '** Remove trailing comma from the day in ss(2) Dim dayString As String = ss(2).ToString ss(2) = dayString.Substring(0, dayString.Length - 1) '** Convert to date (ss(3) contains the year) Dim df As New C_DateFunctions Dim sourceDate As Date = df.BuildDate(ss(1), ss(2), ss(3)) df = Nothing '** Test the procedure by displaying the resulting date MsgBox(sourceDate.ToShortDateString) The test at the end displays the converted date as 5/20/2010.

You're welcome. :) Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles] I only read formatted code with indentation, so please use PRE tags for code snippets. I'm not participating in frackin' Q&A, so if you want my opinion, ask away in a real forum (or on my profile page).

Thanks Luc :)

TheComputerMan wrote: a God amongst programmers :wtf: Hardly. But, I am willing to accept a sacrifice! :laugh: TheComputerMan wrote: Dave said "and whatever is in the InitializeComponent method". Huh? He thinks I have not looked at that a million times. OK, well one last time. 2 clues pointed in that direction after seeing the code. First, the error you originally posted was an unheandled exception. Second, you said it never made an event log entry. That was pretty much the first line of code in the Load handler, so it appears that it never got this far. The order for execution of a Form start's with the contructor, then goes to InitializeComponent, then the Load event is raised, where your Load handler gets called. Those two clues says that either the New method (constructor) failed, but it's rare to find code in a Form's New method, or in InitializeComponent, which New calls by default. Also, You normally don't find Try/Catch blocks in InitializeComponent so the exception most likely came from there. TheComputerMan wrote: groveling on the floor before the greatness of the man You can get up now. I work for a living. I can only wish I could sit around and have my wife feed me grapes all day. A guide to posting questions on CodeProject[^] Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic      2006, 2007, 2008 But no longer in 2009...

you're welcome. sorry, having information in two threads got me confused. It still is too expensive; I don't see why you copy the image, as sourceBitmap = New Bitmap(Image.FromStream(sr.BaseStream)) creates two identical images, the first one is the result of FromStream and is a real Image (and also a Bitmap upcast to an Image), the second the result of your Bitmap constructor is a real Bitmap. And once more, the first never gets disposed of. A simple Image.FromStream(sr.BaseStream) As Bitmap should do (or whatever the VB syntax is for casting from Image to Bitmap). This should halve your CPU and memory load. FYI: the person you reply to normally gets an e-mail notification; as you seem to be replying a lot to yourself, you got lots of e-mails, and I only saw your replies by watching the forum. So I suggest you make sure you reply to (the last message of) the person you want to get the reply and notification... :) Luc Pattyn Have a look at my entry for the lean-and-mean competition; please provide comments, feedback, discussion, and don’t forget to vote for it! Thank you. Local announcement (Antwerp region): Lange Wapper? Neen!

Hi, yes this is placing a statement text into a database table. There are many ' characters in the statements but I only get a problem when using the +. Incidentally the identical code in SQL Server 2005 (as opposed to Compact) does not cause a problem - this is where the SELECT statement is used in the same format as part of an execute to create a stored procedure. In this the +' '+ goes straight in with no problem, but I have not tried storing it I must admit, only executing it.

You forgot: Whine: The previous version of Windows. I wanna be a eunuchs developer! Pass me a bread knife!

I think I have found the answer - it don't work!!! :( From Microsoft Using EXECUTE with a Character String In earlier versions of SQL Server, character strings are limited to 8,000 bytes. This requires concatenating large strings for dynamic execution. In SQL Server 2005, the varchar(max) and nvarchar(max) data types can be specified that allow for character strings to be up to 2 gigabytes of data. Changes in database context last only until the end of the EXECUTE statement. For example, after the EXEC in this following statement is run, the database context is master. USE master; EXEC ('USE AdventureWorks; SELECT EmployeeID, Title FROM HumanResources.Employee;'); Thanks very much for trying anyway! :)

Sorry, jumped the gun. I found the answer. Seems to be a bug you can get round with: Private player As New System.Media.SoundPlayer() Public Sub PlaySound(ByVal sound As Stream) sound.Position = 0 ' Manually rewind stream player.Stream = Nothing ' Then we have to set stream to null player.Stream = sound ' And set it again, to force it to be loaded again... player.Play() ' Yes! We can play the sound! End Sub Apparently when you use the Audio Play it starts the end of the stream for some reason.

Thanks Folks. Question answered in the "How do I..." about the screen saver. Process.start works just fine.

Hi Fabio, Thanks for that. I had pulled the code from another program where I am using it to store the picture in SQL Server and forgot to take that bit out! Duh!! :rolleyes: The corrected code block is: Friend Function GetAvatar(ByVal ContactID As Integer) As Drawing.Bitmap Dim pict As Drawing.Bitmap 'This just gets the file name Dim strFilename As String = cDBHandler.ExtractContactImage(ContactID) Try If strFilename.Trim > "" Then Dim fs As New System.IO.FileStream(strFilename, IO.FileMode.Open, IO.FileAccess.Read) pict = Drawing.Bitmap.FromStream(fs) fs.Close() Else pict = My.Resources.nouserpic\_grey End If Catch ex As Exception pict = My.Resources.nouserpic\_grey End Try Return pict End Function Sorry if that caused any confusion to anyone.