MySQL, a free database engine, is a popular choice among webmasters. Despite its popularity, it is still difficult to visualize the database, table, fields, and data. Though there are many great php web interface solutions available, there are not many software based solutions. My favorite solution is Toad. It is powerful freeware for MySQL and available for download. If you have ever used Microsoft’s SQL Server software, the Toad user interface is will feel similar.
You are given a visual representation of your databases. Select a database and drill down to view the tables. From the tables, you can view either the existing data or view the columns. In addition to viewing the existing tables, you can create new tables, columns, and insert new data.
All in all, Toad is a great free option for MySQL users. If you have never given it a try, I highly recommend you give it a test drive. Included in the functionality is Version Control, Integration, Macro Record and Playback, Database Browser, Security Manager, Knowledge Xpert, Project Manager, SQL Recall, Code Formatter, Import/Export, Analyze Table, Check Table, Compare and Sync, Create/Drop Database, Kill Session, Change Database Variables, Customizing toolbars. Toad has been developed by Quest and can be found at http://www.quest.com/toad-for-mysql/
An updated Article Available at: Easily Convert An Existing Web Form to a Web Content Form (with a Master Page)
To convert an exist ing aspx page without a masterpage site template is easy. We are going to walk through a simple example for which can be applied to other situations. Assume you have the following page called Default.aspx (with it’s associated Default.aspx.cs page which we will not need to worry about).
<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebApplication1._Default" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Hello World</title>
</head>
<body>
<form id="form1" runat="server">
<div>Hello World</div>
</form>
</body>
</html>
Now a standard masterpage with two content place holders (one for header information and the other for the main body content) is created for your web application called Site1.Master. Header and footer text has been added that will appear for every content item.
<%@ Master Language="C#" AutoEventWireup="true" CodeBehind="Site1.master.cs" Inherits="WebApplication1.Site1" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" >
<html>
<head runat="server">
<title>Untitled Page</title>
<asp:ContentPlaceHolder ID="head" runat="server"> </asp:ContentPlaceHolder>
</head>
<body>
Hello World Header!
<form id="form1" runat="server">
<div>
<asp:ContentPlaceHolder ID="ContentPlaceHolder1" runat="server">
</asp:ContentPlaceHolder>
</div>
</form>
Hello World Footer!
</body>
</html>
First, an <%@ Page> tag is should be added to the first line. See resulting code for necessary tag attributes. Any page specific tags from the within the head tags except for <title> are placed inside the <asp:Content ID=”Content1″>. If there are no specific tags, this section will be present, but empty. Likewise, all content in the body (labeled in green in the above example), will be placed into <asp:Content ID=”Content2″>. To give your item template a title, there is a field in <%@ Page> called title which contains the page title (labeled in red in the above example). The final Default.aspx page will be as follows:
<%@ Page Language="C#" MasterPageFile="~/Site1.Master" AutoEventWireup="true" CodeBehind="Default.aspx.cs" Inherits="WebApplication1.WebForm1" Title="Hello World" %>
<asp:Content ID="Content1" ContentPlaceHolderID="head" runat="server">
</asp:Content>
<asp:Content ID="Content2" ContentPlaceHolderID="ContentPlaceHolder1" runat="server">Hello World
</asp:Content>
A regular webpage has now been converted to work with your defined masterpage! You can follow this as a basis to larger more complexed pages.
