Sunday, June 27, 2010





SAVE THIS USING:

LOVE




Unspoken love is like a poison
if you don't spit it out
it will eat you up inside





You can fall in love in an instant
it is letting go that takes time




                     We cannot really love anybody
                     with whom we never laugh with




Love is like a hourglass
with the heart filling up.





Thursday, June 17, 2010

“All About HTML”

What Does HTML Stand for?

HTML is an acronym for hypertext markup language. It is a language that is used to produce documents for the World Wide Web. Using tags and attributes, HTML instructs browsers on how to display the text, hyperlinks and images on a web page. HTML pages are distributed on the web using hypertext transfer protocol (HTTP).

History

  1. In the early 1990s, Tim Berners-Lee wrote the first version of HTML. In 1994, the Internet Engineers Task Force (IETF) created the HTML Working Group, which developed the HTML 2.0 specification. Some web browser developers began to add their own tags to HTML. Many other browsers couldn't support the new tags. In 1994 the World Wide Web Consortium (W3C) was formed to help standardize the World Wide Web. After 1995, the World Wide Web Consortium played an important role in developing new HTML specifications, as did browser vendors.

Function

  1. HTML pages contain information about the fonts, text, text colors, justification, background colors, paragraphs, images, hyperlinks and other elements of a web page. Many tags can take attributes, which provide more information about how the page should be displayed. Web browsers can interpret this information to display the page in a manner which is both appealing and useful. HTML tags and attributes are case insensitive. Therefore is functionally equivalent to . Cascading style sheets (CSS) are often used in place of tags to set the font, background and color of a page or set of pages.

Features

  1. Every page must have an tag and a tag. (anchor) tags create hyperlinks in HTML. (image) tags indicate where images should be displayed on the page and can link to images stored either on the same server or on a different server as the rest of the pages.

    (paragraph) tags show where paragraphs begin and end, whereas
    (line break) tags simply create a single carriage return.
    tags create tables with columns, rows and cells to help organize data and text on the page. HTML can be written in a plain text editor, but there are also WYSIWYG (What You See Is What You Get) editors which simplify the editing process.

    Types

    1. There are two types of HTML markup; physical markup and logical markup. Physical markup specifies the exact method in which a document should be displayed. Logical markup describes the intended function of a string of text. For example, (bold) is physical markup which directly instructs the web browser to display the text in bold. However, is logical markup. A web browser interprets the tag in the best method it is capable of. Therefore, if the browser or computer can't display text in bold (as in a text-only browser), it will display it using a different method that still emphasizes the text.

    Identification

    1. HTML pages can be identified in most cases by their extension. Typically the extension is .htm or .html. They can also be identified by looking at the source code. The and tags will be at both the top and the bottom of the document.

    Effects

    1. HTML creates a series of interlinked pages that can be browsed quickly and easily. The pages are displayed with a clearly legible and organized structure. No matter how a web browser is programmed, it will be able to format a well-written web page effectively. The same page may look different on different browsers, but it will function similarly on each. For example, Internet Explorer will typically display a web page with all font and color information, images and links which can be browsed using a mouse. However the LYNX browser will display the same page in text only, which must be navigated using the keyboard.

Wednesday, March 10, 2010

Tables

A database table is similar in appearance to a spreadsheet, in that data is stored in rows and columns. As a result, it is usually quite easy to import a spreadsheet into a database table. The main difference between storing your data in a spreadsheet and storing it in a database is in how the data is organized.

To get the most flexibility out of a database, the data needs to be organized into tables so that redundancies don't occur. For example, if you're storing information about employees, each employee should only need to be entered once in a table that is set up just to hold employee data. Data about products will be stored in its own table, and data about branch offices will be stored in another table. This process is called normalization.

Each row in a table is referred to as a record. Records are where the individual pieces of information are stored. Each record consists of one or more fields. Fields correspond to the columns in the table. For example, you might have a table named "Employees" where each record (row) contains information about a different employee, and each field (column) contains a different type of information, such as first name, last name, address, and so on. Fields must be designated as a certain data type, whether it's text, date or time, number, or some other type.

Another way to describe records and fields is to visualize a library's old-style card catalog. Each card in the cabinet corresponds to a record in the database. Each piece of information on an individual card (author, title, and so on) corresponds to a field in the database.

Forms

Forms are sometimes referred to as "data entry screens." They are the interfaces you use to work with your data, and they often contain command buttons that perform various commands. You can create a database without using forms by simply editing your data in the table datasheets. However, most database users prefer to use forms for viewing, entering, and editing data in the tables.

Forms provide an easy-to-use format for working with the data, and you can also add functional elements, such as command buttons, to them. You can program the buttons to determine which data appears on the form, open other forms or reports, or perform a variety of other tasks. For example, you might have a form named "Customer Form" in which you work with customer data. The customer form might have a button which opens an order form where you can enter a new order for that customer.

Forms also allow you to control how other users interact with the data in the database. For example, you can create a form that shows only certain fields and allows only certain operations to be performed. This helps protect data and to ensure that the data is entered properly.

Reports

Reports are what you use to summarize and present data in the tables. A report usually answers a specific question, such as "How much money did we receive from each customer this year?" or "What cities are our customers located in?" Each report can be formatted to present the information in the most readable way possible.

A report can be run at any time, and will always reflect the current data in the database. Reports are generally formatted to be printed out, but they can also be viewed on the screen, exported to another program, or sent as e-mail message.

Queries

Queries are the real workhorses in a database, and can perform many different functions. Their most common function is to retrieve specific data from the tables. The data you want to see is usually spread across several tables, and queries allow you to view it in a single datasheet. Also, since you usually don't want to see all the records at once, queries let you add criteria to "filter" the data down to just the records you want. Queries often serve as the record source for forms and reports.

Certain queries are "updateable," meaning you can edit the data in the underlying tables via the query datasheet. If you are working in an updateable query, remember that your changes are actually being made in the tables, not just in the query datasheet.

Queries come in two basic varieties: select queries and action queries. A select query simply retrieves the data and makes it available for use. You can view the results of the query on the screen, print it out, or copy it to the clipboard. Or, you can use the output of the query as the record source for a form or report.

An action query, as the name implies, performs a task with the data. Action queries can be used to create new tables, add data to existing tables, update data, or delete data.

Macros

Macros in Access can be thought of as a simplified programming language which you can use to add functionality to your database. For example, you can attach a macro to a command button on a form so that the macro runs whenever the button is clicked. Macros contain actions that perform tasks, such as opening a report, running a query, or closing the database. Most database operations that you do manually can be automated by using macros, so they can be great time-saving devices.

Modules

Modules, like macros, are objects you can use to add functionality to your database. Whereas you create macros in Access by choosing from a list of macro actions, you write modules in the Visual Basic for Applications (VBA) (Visual Basic for Applications (VBA): A macro-language version of Microsoft Visual Basic that is used to program Microsoft Windows-based applications and is included with several Microsoft programs.) programming language. A module is a collection of declarations, statements, and procedures that are stored together as a unit. A module can be either a class module or a standard module. Class modules are attached to forms or reports, and usually contain procedures that are specific to the form or report they're attached to. Standard modules contain general procedures that aren't associated with any other object. Standard modules are listed under Modules in the Navigation Pane, whereas class modules are not.

Reference: http://office.microsoft.com/en-us/access/HA100644501033.aspx