PlausiblyDamp

Does it start to stay in front of other forms after any particular time or after a certain operation has been done?

Too be honest those 3 really don't make that much difference although if schedules allow I would try to do the 2663 before the 2524 if I hadn't had much exposure to XML.

How is the stored procedure defined? Specifically check the order you add the parameters matches the order they are declared - IIRC oledb commands do not support named parameters.

Have you tried not putting the sigle quotes around the 0?

Me.Icon = Nothing

Just use a normal integer variable to do the counting and convert it to a string representation of a binary value with code like Dim i as integer = 12345 Dim s as string s = Convert.ToString(i, 2)

Creating your own control from scratch would be an awful lot of work if you are doing it properly, is there any reason why you couldn't inherit from Textbox and just add your own functionality or override existing methods to get the end result you desire?

If you are doing the 2310 then there is no real reason to do the 2640 as they cover similar ground the 2640 is just shorter as it assumes more prior knowledge. I would personally recomend doing the 2310 before the 2389 as the 2310 will give you an introduction to ADO.Net as part of the course which makes the concepts covered in the 2389 easier to follow. If you have little or no SQL experience then I would recomend you take the 2071 first as the 2073 assumes a working knowledge of T-SQL and as such doesn't take the time to cover the basic concepts. In terms of prior knowledge the 2071 assumes very little, the 2073 more (see above point). The 2310 assumes very little web development but familiarity with one of more .Net languages (the course is run using C# and VB.Net) - if you can write a basic class and one or two methods you should be ok. Regarding 2005 it really depends on the proposed timeframes, the product itself isn't due till November and the only available courses currently are designed in part as upgrading existing .Net skills to 2005...

Does it give any errors? How exactly is it not working? Are you using exactly that code or has it been modified in any way?

Code generation and reverse engineering are built in via the class designer. It doesn't come close to supporting all the UML document types though so if you like sequence diagrams etc you will need to resort to 3rd party tools.

With sortKey .ParameterName = "SORTKEY" .OracleType = OracleType.Cursor .Direction = ParameterDirection.Output End With is that correct? The stored proc defines sortKey as VARCHAR2 rather than a cursor.

Oracle isn't my strong point but you might try creating and configuring the parameters and then adding them to the command. If that doesn't help post back here and I'm sure somebody may be able to help.

Could you not just call CreateProcess and then exit without waiting or closing the handle yourself?

Arrays are reference types, the code Dim BalanceArrayPlus() As Double = BalanceArray simply creates another variable that points to the same array in memory. IIRC you will need to look at Array.Copy(...) to perform a deep copy of the array.

The CLRProfiler tool can be useful to find what resources are being allocated where, it can be found here

Default instances are defined by an attribute - if you do not apply the attribute then you do not get a default instance. As far as I am aware (do not have VS 2005 on this PC) default instances are lazy so there shouldn't be too much in terms of overhead.

Does either function change any of the values in the arrays passed in? If so that is possibly a cause of the problem

could you post the declaration for the two functions then? Also when you say the second call is 0 do you mean it returns 0? If so are the parameters you passing in correct?

Try putting Option Strict On at the top of the source file and fix any errors it throws up, also could you post the code for the 2 functions themseleves?

Do you get any errors generated? If you step through the code in the debugger what happens?

http://www.xtremedotnettalk.com/showthread.php?t=87690

If this code is running on the web server then the ASPNET account will most likely need to be granted permissions to the printer, also be aware this will probably result in the printer attached to the web server being used not a client side printer.

How are you compiling / executing the script? Could you post either the code or a simplified version that demonstrates this problem?

His ban should be lifted the start of October.

Generics can be useful in other scenarios as well as collections: The typical C style Min and Max macros or a simple Swap function that take two parameters of the same type can be very easily implemented via a generic - try doing the same without them. Generic interfaces - e.g. IComparable<T> so you do not have to provide your own object / type checks and conversions remove a chunk of cut and paste style code when compared to a non generic version. If anything I see generics reducing the amount of error checking / casting code rather than cluttering up the source. In terms of language simplicity I feel VB.Net 2 is going more that route (default form instances being one example) but without limiting you to just the simplified approach.