Ask for your tasks to given to you in writing. Apart from giving you something to refer back to it is also "evidence" of what you were asked to do which can help you avoid "scope creep" (where users ask for more and more features to be slipped in within the same timescales) You can then go over the scenarios / requirements in your own time at your own pace to get as much understanding as possible. If you have questions, or don't quite get something, then collate all of your questions and go back to your QA with them. Go through those points one-by-one and make notes against the original document. Confidence can be upset if you feel you are under pressure, so try to always be prepared ... keep a notebook (and pen!) handy always so you can take notes of anything you're not sure of - then you can do your research or thinking away from that pressure. Don't forget the other advice here - I dont remember code of last week[^] - it will help too

Locate a Training Center Near You[^] "My interest is in the future because I'm going to spend the rest of my life there." - Charles F. Kettering

Ah, now that makes sense! I can certainly see how technical issues can inhibit implementation; I hope they really are trying to resolve them. P.S. And mixins sound like a good idea too.

Have you heard of Google[^]? If at first you don't succeed, you're not Chuck Norris.

Here's a start![^] If at first you don't succeed, you're not Chuck Norris.

No, you cannot stop the .NET framework. This would even be dangerous, as it would halt the execution of all applications that are using the framework. Can you tell us what you're trying to achieve? Perhaps there's an alternative method to reach that goal. If the target is a Windows Service, then yes - those can be paused, started and stopped. I are troll :)

I have wrote a program to get the file system with folders and files up to leaf nodes without using recursion. If you are interested you can send a mail to kanagarajmk@gmail.com

There isn't a de facto app for testing. You can use ANY product that records keystrokes/mouse-events and plays them back for blackbox-testing. For white-box testing, I'd recommend the Visual Studio debugger. You might want to dive into TDD[^]. I are troll :)

Simon Stevens wrote: A Car is-a vehicle and a car also is-a ManMadeItem, but this forms a hierarchy (Car->Vehicle-ManMadeItem) so multiple inheritance isn't needed I don't think I'd regard that as a hierarchy, because a horse could also be regarded as a Vehicle even though it is not a ManMadeItem. I think the simplest way to look at the issues of inheritance versus interface is that an inherited base class can supply default fields and methods which are then usable by child classes; an interface not only does not provide default storage for fields and code for methods, but it can't even bind them by default. If an object inherited from Class1 and Class2, both of which provided a Smile method, it would be unclear whether TheObject.Smile was supposed invoke Class1.Smile or Class2.Smile. With interfaces, however, there is no problem. TheObject must have an "implements" line for every interface method it supports, indicating what method should be used for Interface1.Smile and which one should be used for Interface2.Smile. Further, to actually use either of those methods on an object, the object must first be cast to Interface1 or Interface2. Thus, there is no ambiguity.

Here is an example: BEGIN TRANSACTION select * from employee ROLLBACK This is syntactilly correct, but logically not very valid. A SELECT statement does not change the database, therefore a commit or rollback really does nothing except end the transaction. The above example should really should never be used, by starting a transaction you could be creating unnecessary locks to be granted. Transactions are typically used to guarantee that ALL updates are made or NO updates are made. For example: (syntax is not 100% accurate, but you should get the idea) BEGIN TRANSACTION try UPDATE table1 set newbalance = newbalance - 100 where ID=ABC INSERT into audittable values (NOW(),'ABC','WITHDRAWL') COMMIT catch ex ROLLBACK end try This example shows that 2 tables are being updated and if they are successful, the transaction is committed, if there is an error then a rollback is performed.

Hi, what u can do is replace SELECT * FROM user with SELECT * FROM [user] then it will get recognized as a table name... living life on the flip side

waqarnaeem2@hotmail.com wrote: what is the meaning of unicode in sql? The same as it means elsewhere I would presume. It is a form of character encoding. *Developer Day Scotland - Free community conference *Colin Angus Mackay's Blog *Latest Scottish Developers Newsletter Vogon Building and Loan advise that your planet is at risk if you do not keep up repayments on any mortgage secured upon it. Remember that the force of gravity can go up as well as down.

waqarnaeem2@hotmail.com wrote: there is confusion Indeed there is. I'm having some difficulty parsing your question. waqarnaeem2@hotmail.com wrote: clustered index is 1 in table There can only be one clustered index in a table. waqarnaeem2@hotmail.com wrote: they match the physical & logical records The physical rows kind of follow the clustered index. It isn't exact, but the general idea is that the rows are physically sequenced by the clustered index however, SQL Server performs many optimisations that means that it doesn't follow that except in the simplest of circumstances. waqarnaeem2@hotmail.com wrote: so what nonclustered index is more than 1 in a table You can have many non-clustered indexes on a table. waqarnaeem2@hotmail.com wrote: How they work?? The same way as an index in a book. The non-clustered area consists of a number of pages which contain look up information that can be used to find the physical rows faster than you would be able to if you had to scan the whole table to find the same information. waqarnaeem2@hotmail.com wrote: then they increase the congestion 2much What congestion? They will requires a little more IO for the lookup, but the idea is that the extra up-front work pays off as you can find the actual data much faster and using less IO overall. In some queries there may even be enough information in the index to never need to look at the physical rows at all. This makes everything much faster and less congested. However, when you insert, update or delete from a table with non-clustered indexes you have to remember that SQL Server will also have to update the indexes as well as the actual physical row. waqarnaeem2@hotmail.com wrote: y prefer 1 to another in what sense? If you want more than one index on a table then you have no choice as you must use a non-clustered index at some point. Typically the clustered index is on your primary key *Developer Day Scotland - Free community conference *Colin Angus

Take a look this http://www.w3schools.com/sql/sql_join.asp[^] I Love T-SQL "Don't torture yourself,let the life to do it for you." If my post helps you kindly save my time by voting my post.

waqarnaeem2@hotmail.com wrote: well if i want to do something by method overloading ,, that can also be done by overloading the constructors & then using the concern method,? Be confused for this description... waqarnaeem2@hotmail.com wrote: why we need a delegate??why we need to encapsulate a method in an object?? You can treat delegate as a safe function pointer. Maybe a beginning book is right way to start. :) I Love KongFu~

Isn't it? :-D If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler. -- Alfonso the Wise, 13th Century King of Castile. This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong. -- Iain Clarke [My articles]

If you have trouble moving from C++ to Java, then you didn't use C++ correctly. If you are learning either one for the first time, Java is about 2x easier. Very recent Java has introduced generics, which is a massive headache. But guess what? C++ already had them, and they aren't any easier there. And "to select your layout"? If you are talking about GUI design, that depends entirely on what you are doing and what tools you are using. If you are using Eclipse, you may have trouble designing GUIs. NetBeans IDE does them every bit as easily as MS Visual Studio does C++ GUIs. Personally, using SpringLayout, I can code GUIs by hand in Java and they are a lot simpler to read. Don't let my name fool you. That's my job.

Do you mean method overloading and constructor overloading? They are much the same, except constructor overloading enables you to create your object instances from different signatures that cn be used for initialization. Method overloading enables different method implementations to be called depending on the signature. Dave BTW, in software, hope and pray is not a viable strategy. (Luc Pattyn) Visual Basic is not used by normal people so we're not covering it here. (Uncyclopedia)