Sathyaish
September 25th, 2003, 01:12 PM
I've begun learning CSS and have written an HTML page with a link to an external style sheet called MyFirstStyleSheet.css. Sadly, the code in the style sheet is not reflected in the format of the contents of the HTML.
They're both in the same folder.
Here's the style sheet code:
DIV.FOOTNOTE {FONT-STYLE: italic; align: center;}
P {FONT-FAMILY: Verdana; FONT-STYLE: italic;}
DIV.LINKS {COLOR: green;}
I copied some content from the Net and put it into the body tag of an HTML. Here it is:
<HTML>
<HEAD>
<LINK REL=stylesheet HREF="MyFirstStyleSheet.css" type="txt/css" />
<TITLE>My first stunt in using a style sheet</TITLE>
</HEAD>
<BODY>
<H1>Developing a VBScript Class for an Extremely Lightweight Recordset Alternative </H1>
<H2>Using ADO .NET - First Principles </H2>
<HR/>
<H3>Part 1 - Learning ADO .NET </H3>
<P>
You can do a lot with Visual Basic by itself, but ultimately, you have to have data to build most systems. VB .NET is designed to work with a new way to access data:
ADO .NET.</P>
<P>
The name "ADO .NET" was invented by Microsoft Marketing and you should not conclude that it's "just like ADO". Like VB .NET itself, ADO .NET is a completely
new product with only a surface similarity to earlier versions. That's why it doesn't really matter that ADO once stood for ActiveX Data Objects. It doesn't stand for that
anymore.</P>
<P>
In this series, we're going to learn ADO .NET literally from the ground up - slowly and carefully. The series will be presented in "byte sized" articles rather than trying to
tell the story all at once. Also, important issues that you have to know, but are not part of the main focus, are presented as "DYK" articles so you can read them if you
need to, or get on to the main topic if you don't.</P>
<P>
About.com also has a database focused site at databases.about.com. This series will focus on the VB .NET language aspects of ADO .NET. Go to About Databases for
more information 'About' building and using databases.</P>
<H3>Abstract</H3>
<P>
Why in the world would we consider replacing the venerable old ADO Recordset object? It certainly serves its purpose on about a trillion web pages around the world.
However, given how many ASP pages simply need to write out HTML data from it, it’s remarkably over-loaded with unused and unnecessary features. Each unused
feature is another waste of system resources. In this article, Tom Kelleher shows how to build a VBScript class to replace the Recordset as our data container, freeing
up those resources… and how he stumbled across some interesting additional uses in the process.</P>
<H3>Platform</H3>
<P>
The object described in this article was originally developed and deployed on a Windows NT Server v4.0 system with 512 MB of RAM, running ASP 2.0, IIS 3.0,
VBscript 5.6, and ADO 2.6. However, these are not the minimum requirements for it. ADO 2.1 would suffice to pull database data, VBScript 5.0, and lower RAM would
all work. Also, the object has since been installed on a Windows 2000 Server SP2, with ASP 3.0, IIS 5.0 and more RAM with no ill effects.</P>
<DIV>
<HR/>
<FOOTNOTE>
Sathyaish Chakravarthy
The author works as a Senior Project Leader with FCS Software Solutions Ltd.
</FOOTNOTE>
<HR/>
<LINKS>
<DIV left=20px>VB Links</DIV>
<DIV left=100px>Source Code</DIV>
<DIV left=180px>Forums</DIV>
<DIV left=300px>Visual Basic for Applications</DIV>
</LINKS>
<DIV>
</BODY>
</HTML>
What could be the problem?
They're both in the same folder.
Here's the style sheet code:
DIV.FOOTNOTE {FONT-STYLE: italic; align: center;}
P {FONT-FAMILY: Verdana; FONT-STYLE: italic;}
DIV.LINKS {COLOR: green;}
I copied some content from the Net and put it into the body tag of an HTML. Here it is:
<HTML>
<HEAD>
<LINK REL=stylesheet HREF="MyFirstStyleSheet.css" type="txt/css" />
<TITLE>My first stunt in using a style sheet</TITLE>
</HEAD>
<BODY>
<H1>Developing a VBScript Class for an Extremely Lightweight Recordset Alternative </H1>
<H2>Using ADO .NET - First Principles </H2>
<HR/>
<H3>Part 1 - Learning ADO .NET </H3>
<P>
You can do a lot with Visual Basic by itself, but ultimately, you have to have data to build most systems. VB .NET is designed to work with a new way to access data:
ADO .NET.</P>
<P>
The name "ADO .NET" was invented by Microsoft Marketing and you should not conclude that it's "just like ADO". Like VB .NET itself, ADO .NET is a completely
new product with only a surface similarity to earlier versions. That's why it doesn't really matter that ADO once stood for ActiveX Data Objects. It doesn't stand for that
anymore.</P>
<P>
In this series, we're going to learn ADO .NET literally from the ground up - slowly and carefully. The series will be presented in "byte sized" articles rather than trying to
tell the story all at once. Also, important issues that you have to know, but are not part of the main focus, are presented as "DYK" articles so you can read them if you
need to, or get on to the main topic if you don't.</P>
<P>
About.com also has a database focused site at databases.about.com. This series will focus on the VB .NET language aspects of ADO .NET. Go to About Databases for
more information 'About' building and using databases.</P>
<H3>Abstract</H3>
<P>
Why in the world would we consider replacing the venerable old ADO Recordset object? It certainly serves its purpose on about a trillion web pages around the world.
However, given how many ASP pages simply need to write out HTML data from it, it’s remarkably over-loaded with unused and unnecessary features. Each unused
feature is another waste of system resources. In this article, Tom Kelleher shows how to build a VBScript class to replace the Recordset as our data container, freeing
up those resources… and how he stumbled across some interesting additional uses in the process.</P>
<H3>Platform</H3>
<P>
The object described in this article was originally developed and deployed on a Windows NT Server v4.0 system with 512 MB of RAM, running ASP 2.0, IIS 3.0,
VBscript 5.6, and ADO 2.6. However, these are not the minimum requirements for it. ADO 2.1 would suffice to pull database data, VBScript 5.0, and lower RAM would
all work. Also, the object has since been installed on a Windows 2000 Server SP2, with ASP 3.0, IIS 5.0 and more RAM with no ill effects.</P>
<DIV>
<HR/>
<FOOTNOTE>
Sathyaish Chakravarthy
The author works as a Senior Project Leader with FCS Software Solutions Ltd.
</FOOTNOTE>
<HR/>
<LINKS>
<DIV left=20px>VB Links</DIV>
<DIV left=100px>Source Code</DIV>
<DIV left=180px>Forums</DIV>
<DIV left=300px>Visual Basic for Applications</DIV>
</LINKS>
<DIV>
</BODY>
</HTML>
What could be the problem?