EndNote X7 Windows: Install Word 2016 CWYW Toolbar

The tools may need to be manually added to Word if they do not appear:

1. Browse to the Word 2016 folder: 
   "C:\Program Files (x86)\Microsoft Office\Office16." 
2. Right-click WINWORD.EXE and select "Run as Administrator" to open Word 2016 with Administrative rights.
3. Go to the File Menu and choose "Options."
4. Select "Add-Ins" from the list at the left.
5. At the bottom of the Add-Ins page, there is a "Manage:" dropdown list. Leave this on "COM Add-ins" and select Go.
6. On the COM Add-Ins page, Choose the "Add..." button.
7. Browse to the following location and select the "EndNote CWYW.dll" file.
   C:\Program Files (x86)\Common Files\ResearchSoft\Cwyw\17
8. Once you have Selected the "EndNote CWYW.dll" file, choose OK and OK again to close the COM Add-Ins screen. The EndNote tools should now be in Word.

For more options read this : https://researchsoftware.com/faq/endnote

Email Etiquette Tips

Subject Line: 

• Be short, yet clearso readers know what you're writing about and can find your note later.
• Indicate urgency and whether action is required. For example: "Cust Sat Issue-Need response today"

Body of Note: 

• State the objective of your message in the first line: "This is to ask for your approval....."; "This is to invite you..."; etc.. This lets the recipient know right away what action is needed.
• Be concise.
• Choose words carefully.
• Write with the audience in mind.
• Limit your message to one subject.
• Limit your message to 25 lines... about one computer screen.
• Use bulleted lists when appropriate.
• Use "sections" ("twisties") where appropriate in longer notes.
• Keep paragraphs short.
• Add a blank line between paragraphs.
• Use bold type to highlight main points.
• Don’t SHOUT ... using ALL CAPITAL LETTERS is considered shouting.

Etiquette: 

• Don’t send blanket messages to everyone on a distribution list if only 3 or 4 people need the information.
• The recipient who needs to take action, should be directly addressed in the TO field and the greeting/opening of the note.
• Recipients copied (CC'd) on a note should not be expected to take action. It's FYI only.
• When marking e-mail urgent, ask yourself the question "Is urgent action really required by the recipient?" Only send urgent e-mail if the answer is yes.
• Don’t forward large-file attachments unless you know the recipient wants or needs them. (Use Connections to share large files).
• Don’t forward trails of notes unless it's necessary to make sense of your note.
• Don’t use e-mail to address "emotional" topics. Speak directly.
• Ensure that you have a footer on your e-mails -- your name and contact details such as your phone number.

Thought Provokers: 

• People will learn about you from the e-mail you send. Ensure your communication is courteous and professional.
• Get to know the communication style of those with whom you communicate frequently. How often do they access their e-mails? Do they prefer urgent messages by e-mail, instant message or phone?

CDI Best Practices with Real-Life Examples [TUT3287] @JavaOne16

CDI Best Practices with Real-Life Examples [TUT3287]

Session ID: TUT3287
Session Title / Download Link : CDI Best Practices with Real-Life Examples [TUT3287]

Session Type: Tutorial Session
Session Abstract:
As the adoption of Contexts and Dependency Injection (CDI) for Java EE API grows, it is important to understand how to use CDI effectively to maximize the benefits of using a loosely coupled, type-safe, annotation-driven dependency injection solution. This session outlines the best practices for using CDI, such as annotations versus XML, @Named as a qualifier, qualifier type safety versus verbosity, effective use of producers/disposers, using scopes properly, best practices for using conversations, defining effective stereotypes, interceptors versus decorators, static versus dynamic injection/lookup, CDI versus Java EE resource injection, using CDI with EJB 3.1, CDI/JSF 2 integration patterns, and CDI/JPA 2 usage patterns.

Create First CDI Application

1- Create new Netbeans Project named "CDI_JavaOne16_TUT3287_Demo"

2- Edit the "Web.xml"

<servlet-mapping>
        <servlet-name>Faces Servlet</servlet-name>
        <url-pattern>*.xhtml</url-pattern>
</servlet-mapping>

and 

<welcome-file-list>
        <welcome-file>index.xhtml</welcome-file>
</welcome-file-list>

3- Run the project
Is it works OK

4- Start our coding

5- create a POJO Bean named "HelloWorld"
5.1 - add method
    public String sayHello(){
        return "Hello User from CDI !";
    }

6- create Managed bean for the page named "HelloManagedBean" with request scope
import javax.enterprise.context.RequestScoped;
6.1 - Inject the bean
    @Inject
    private HelloWorld helloWorld;

6.1 - add action method
    public String sayHelloAction() {
        System.out.println("com.javaone.cdi.secOne.hello.beans.HelloManagedBean.sayHelloAction() : " + helloWorld.sayHello());
        return null;
    }

7- craete page named "HelloPage.xhtml"
7.1 - Add <h:form>
7.2 - add command button <h:commandButton value="Say Hello" action="#{helloManagedBean.sayHelloAction}"/>

8- Activate CDI by adding the beans.xml
8.1 - update the configuration to be  bean-discovery-mode to be "all"
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://xmlns.jcp.org/xml/ns/javaee"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xsi:schemaLocation="http://xmlns.jcp.org/xml/ns/javaee http://xmlns.jcp.org/xml/ns/javaee/beans_1_1.xsd"
       bean-discovery-mode="all">
</beans>

9- Run

How to handle percent (%) underscore (_) and quotes within SQL LIKE queries

Oracle handles special characters with the ESCAPE clause, and the most common ESCAPE is for the wildcard percent sign (%), and the underscore (_).  For handling quotes within a character query, you must add two quotes for each one that is desired.

--Retrive columns name ends with underscore for owner 'XYZ'
select  *
from all_tab_columns
where owner = 'XYZ'
and column_name like '%\_' escape '\'
order by table_name , column_name
;

SQLSERVER: How to alter an existing table int primary key to become an identity column?

Here's a great feature in SQL Server Management Studio SSMS that saved my day.

In SSMS 

1. Go to Options -> Designers -> Table and Database Designers,
2. Check "Auto generate change scripts" and uncheck "Prevent saving changes that require table re-creation".

In object explorer

1. Go to you table and select the column that will get the Identity specification. Right click and select modify. 
2. In the Column properties panel, expand the tree "Identity Specification" and change "(Is Identity)" to yes. Now on the upper left size, select the icon "Generate script". 
3. Pay attention to the warning messages.

Now you will have a generated script that will drop all your constraints, recreate the table with identity, and recreate the constraints. WOW!

Extras::::> Everything worked fine. Also what I need is script to reproduce the modification in our clients installations. and I got it!!!