One of the most annoying things in developing web pages is handling the “Enter key” for form submission. Enter key has been the favourite way users like to submit forms. Though we provide Buttons to click on, the easiest and intuitive way is that, I can enter some text, make some changes and then hit “Enter” to accomplish my submission.
“Enter” Key is handled in a little tricky way by uplevel browsers like Internet Explorer, when it comes to ASP.NET.

* If there is a single Textbox and single button, then it becomes straight forward, the button is submitted. However, the event code doesnt get executed, though the page postsback.

* If there are two or more, buttons, then it takes up the first button as the default button. However, it still doesnt execute the event handler but just refreshes the page.

You can supress the Enter key event using Javascript. But this would result in other undesirable effects like, any Enter key in the form i.e. within Text Area or basically where large text is entered, would be disabled.

The earlier work around was to associate a javascript function to each Button to verify the that the relevant button is submitted upon Enter key.

ASP.NET 2.0 introduces a wonderful work around for this. By simply specifying the “defaultbutton” property to the ID of the <asp:Button>, whose event you want to fire, your job is done.

The defaultbutton property can be specified at the Form level in the form tag as well as at panel level in the <asp:panel> definition tag. The form level setting is overridden when specified at the panel level, for those controls that are inside the panel.

Also, the Event Handler for the specified button, fires thereby simulating a true submit button functionality.

The following sample code contains a form and 4 panels with each of them containing different buttons. It can be noticed that for each panel, there is a default button specified which would trigger the corresponding button’s event handler when “Enter” Key is pressed upon a text changed event.

System.Drawing.Color

<PagerTemplate>
      <asp:LinkButton CommandName="Page" CommandArgument="First"
        ID="LinkButton1" runat="server" Style="color: white">
        &lt;&lt;First</asp:LinkButton>
      <asp:LinkButton CommandName="Page" CommandArgument="Prev"
        ID="LinkButton2" runat="server" Style="color: white">
        &lt; Prev</asp:LinkButton>
      [Records <%= GridView1.PageIndex * GridView1.PageSize %>
        - <%= GridView1.PageIndex * GridView1.PageSize +
           GridView1.PageSize - 1 %>]
      <asp:LinkButton CommandName="Page" CommandArgument="Next"
        ID="LinkButton3" runat="server" Style="color: white">
        Next &gt;</asp:LinkButton>
      <asp:LinkButton CommandName="Page" CommandArgument="Last"
       ID="LinkButton4" runat="server" Style="color: white">
        Last &gt;&gt;</asp:LinkButton>
</PagerTemplate>

Como estamos na ‘Era Digital’, foi necessário rever os velhos ditados existentes e adaptá-los à nova realidade.

Vejam alguns:
1. A pressa é inimiga da conexão.
2. Amigos, amigos, senhas à parte.
3. Antes só, do que em chats aborrecidos.
4. A arquivo dado não se olha o formato.
5. Diga-me que chat freqüentas e te direi quem és.
6. Para bom provedor uma senha basta.
7. Não adianta chorar sobre arquivo deletado.
8. Em briga de namorados virtuais não se mete o mouse.
9. Em terra off-line, quem tem um 486 é rei.
10. Hacker que ladra, não morde.
11. Mais vale um arquivo no HD do que dois baixando.
12. Mouse sujo se limpa em casa.
13. Melhor prevenir do que formatar.
14. O barato sai caro. E lento.
15. Quando a esmola é demais, o santo desconfia que tem vírus anexado.
16. Quando um não quer, dois não teclam.
17. Quem ama um 486, Pentium 5 lhe parece.
18. Quem clica seus males multiplica.
19. Quem com vírus infecta, com vírus será infectado.
20. Quem envia o que quer, recebe o que não quer.
21. Quem não tem banda larga, caça com modem.
22. Quem nunca errou, que aperte a primeira tecla.
23. Quem semeia e-mails, colhe spams.
24. Quem tem dedo vai a Roma.com
25. Um é pouco, dois é bom, três é chat ou lista virtual.
26. Vão-se os arquivos, ficam os back-ups.
27. Diga-me que computador tens e direi quem és.
28. Há dois tipos de pessoas na informática. Os que perderam o HD e os que ainda vão perder…
29. Uma impressora disse para outra: Essa folha é sua ou é impressão minha.
30. Aluno de informática não cola, faz backup.
31. O problema do computador é o USB (Usuário Super Burro)…
32. Na informática nada se perde, nada se cria. Tudo se copia… e depois se cola.

“Não é possível iniciar o microsoft office outlook. Não é possível abrir a janela do Outlook.”

Erro ao abrir o Outlook 2007 (Não é possivel abrir a janela do outlook)
Hoje depois de um reboot ao PC não estava a conseguir abri o Outlook.

Após alguma pesquisa e debug, lá encontrei a solução: “Limpar e gerar novamente o painel de navegação do perfil actual.”

Para isso basta ir ao “Menu Iniciar”, escolher a opção “Executar” e escrever o comando outlook  /resetnavpane

Outros comandos que podem ser úteis para o Outlook:
http://office.microsoft.com/pt-pt/outlook/HP010031102070.aspx
http://www.mundibrasil.org/news/atualizacao-pode-causar-pane-no-outlook-saiba-como-resolver.html

This can happen when you have different versions installed. For example, if you install SQL Server 2005 SP3 and later, and only then install the Reporting Services.

In this situation it should be rerun after the SP3 installation of Reporting Services

The Group Policy Management Console is included in Windows Server 2008; however, you must install it before you can use it. The domain controller promotion process installs GPMC on the server, in addition to adding the domain controller to the domain. Additionally, you can install GPMC on a member server as long as it’s a member of the domain. Let’s look at two ways to install GPMC on Windows Server 2008 (other than through DCPROMO).

Installing GPMC using Server Manager (Windows Server 2008)

The Group Policy Management Console is a Feature in Windows Server 2008. You install Features using Server Manager. Once installed, you can access the feature using Server Manager or you can the specific management console (like gpmc.msc).

1. Open Server Manager by click Start and then point to Administrative Tools. Click Server Manager
2. Click Features in the console tree. In the Features pane, click Add Features
3. Select Group Policy Management from the list of available features in the Add Feature Wizard. Click Install.
4. Start using GPMC or close Server Manager.

There’s another way to install GPMC using Server Manager, which usually installs quicker that using the Server Manager user interface. Server Manager includes a command line utility for installing Features and Roles named ServerManagercmd.exe.

Installing GPMC from the Command Line

1. Open an elevated command prompt.
2. In the command prompt, type ServerManagercmd –install gpmc
3. Start GPMC from the command prompt by typing start gpmc.msc
4. Close the command prompt.

Installing GPMC on Windows Vista Service Pack 1

Installing GPMC on Windows Vista Service Pack 1 can be a little confusing. First, you must download the Remote Server Administration Tools for Windows Vista Service Pack 1 before you can install GPMC. You may remember that GPMC was included in Windows Vista RTM; however Service Pack 1 removes it. After installing RSAT, you then want to install GPMC. Installing RSAT simply includes the Remote Server Administration tools on the Windows Vista SP1 computer but does not deploy for use—you’ll want to choose which RSAT tools you want used on the computer.

1. Download and install the Remote Server Administration Tools (http://go.microsoft.com/fwlink.?LinkID=95703).
2. After the installation is complete, then click Start, click Control Panel, and then click Programs.
3. Click Turn Windows Features on or off from Programs and Features.
4. Click Remote Server Administration Tools and then click Feature Administration Tools from the Windows Features dialog box.
5. Click Group Policy Management Tools and click OK to complete the installation.

You’ll now see Group Policy Management included under the list of Administrative Tools (On Vista, you may need to actually show the Administrative Tools on the start menu – this can be done through Control Panel –> Taskbar and Start Menu –> Start Menu –> Customize –> System Administrative Tools). You can also start GPMC from the command line or run/search menu by typing gpmc.msc.

Source:  blogs.technet.com

Free Currency Converter available in http://www.galhano.com/web/Services/?Action=CC