"Artificial" intelligence. "(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal

The member is question seems to have a pathological aversion to using Google for themselves. :sigh:

i found it...here it is Under Trace properties > Events Selection tab > select show all columns. Now under column filters, you should see the USERNAME name. Give username in following fig. [screen shot image] tbhattacharjee

Tridip Bhattacharjee wrote: looking for help Try asking the person who wrote the code.

Tridip Bhattacharjee wrote: please tell me a solid scenario when people feel right to choose factory method pattern. thanks IDbConnection.CreateCommand(); Doesn't even take parameters :) Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)

Tridip Bhattacharjee wrote: please guide me regarding above definition. Open this page[^], and scroll down to the answer that begins with "Let's understand difference between Factory and FactoryMethod with an example". Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)

https:// www.codeproject.com/ Articles/ 9153/ ASCII-art-with-C :| Luc Pattyn [My Articles] Nil Volentibus Arduum

A simple example of using DbProviderFactory can be found here[^]. Since you already worked with databases I'm going to assume that you'll recognize most parts; note that we ask the Factory to create a connection for us, instead of creating one ourself. The factory can also create IDbCommands, but I prefer to use the factory-method that is provided in the IDbConnection-interface. Details on the class can be found on MSDN[^]. The factory does NOT make your code database vendor-independant - it just makes it easier to switch between those classes. Your C# code would no longer depend on a specific implementation, but chances are that you are using an SQL dialect that is specific to the database-server. Stick to SQL92 if you want to minimize the risc of incompatibilities. Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)

Never thought about using Google for such basic researches ? Patrice “Everything should be made as simple as possible, but no simpler.” Albert Einstein

How about doing your own research for a change? :mad: Git - Wikipedia[^] "These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer

Tridip Bhattacharjee wrote: searching google for merge join in sql server brings lots of result but i like to know when it is good or should i do it when joining one key is pk or other key is fk or regular key. Try reading the first pages that come back as a result :| Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)

"Review" for what? How do you measure "success"? Machine learning involves calculating "distances" from some "ideal". You need to "classify" your problem (i.e. what are the "measures") before you can achieve anything meaningful. Unless you actually have some "good code" as a reference and for "training" purposes, you will get nowhere. "(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal

- call your timer (for example) every Minute - set timer.tick to 60000 - when you have the timer.event don't stop the timer - compare if now is greater or equal your schedule-time, but less your schedule-time +30 seconds - if yes the give the message and increase your schedule-time

Functional programming mayhem. Reap now what you sow. "(I) am amazed to see myself here rather than there ... now rather than then". ― Blaise Pascal

PUT RFC-2616 clearly mention that PUT method requests for the enclosed entity be stored under the supplied Request-URI. If the Request-URI refers to an already existing resource – an update operation will happen, otherwise create operation should happen if Request-URI is a valid resource URI. PUT /questions/{question-id} PUT method is idempotent. So if you send retry a request multiple times, that should be equivalent to single request modification. Use PUT when you want to modify a singular resource which is already a part of resources collection. PUT replaces the resource in its entirety. Use PATCH if request updates part of the resource. Generally, in practice, always use PUT for UPDATE operations. POST The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URI in the Request-Line. It essentially means that POST request-URI should be of a collection URI. POST /questions POST is NOT idempotent. So if you retry the request N times, you will end up having N resources with N different URIs created on server. Use POST when you want to add a child resource under resources collection. Always use POST for CREATE operations.

open powerpoint in web browser - Google Search[^]

That's not your original code. You don't have the control over which slide is shown using the webbrowser control method. A guide to posting questions on CodeProject Click this: Asking questions is a skill. Seriously, do it. Dave Kreskowiak

What you should do is find out how to do it manually, and once you know nomenclature, you'll know how to google how to do it in code. Here's a place to start: [Import data from Excel into PowerPoint - PowerPoint](https://support.office.com/en-us/article/Import-data-from-Excel-into-PowerPoint-3ec295e9-1bfd-47ff-8d7d-8b838caef853) ".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

Yes, you are right. But storing is only necessary if you want to track this kind of information (the local time of the system that has created the time stamp). This is often not necessary because you usually show local times using the time zone of the system displaying the time. If for example a time stamp is created by a user in India and another user somwhere in the U.S. is viewing the related data, it makes more sense to show it in the local time of the viewer or even UTC rather than using the Indian time.