I have created a database connection (asp.net option) using the results
wizard and the page it created is using C# as its default language. It has
also created the global.asa and web.config. Why does it have to do this when
the asp.net code to connect to a database is so simple (according to my
programmer)? I would have liked to learn the basics of asp.net programming
by following what FP does (like I have with HTML) but I now think it would
be easier to knuckle down and learn it myself.

How can I get FP to write in VB instead of C#. Do, or should I, change the
page settings to VB. Should I do that with any site that has and VB in
asp.net?

Can I write to the database using the Results Wizard or other wizard? I was
told that FP only reads data through the wizard.

Why and what is <meta name="ProgId"
content="SharePoint.WebPartPage.Document"> when using the asp.net results
wizard? Surely, I don't need Share Point?

Hope there's net too many questions there

Thanks

>-----Original Message-----
>I have created a database connection (asp.net option)
>using the results wizard and the page it created is
>using C# as its default language. It has also created
>the global.asa and web.config. Why does it have to do
>this when the asp.net code to connect to a database is
>so simple (according to my programmer)?

FrontPage stores ASP.NET database connection info in the
web.config file so that multiple pages can use the same
connection information. This is also good practice if you
write your own code.

All ASP.NET applications have a global.asax file.

I don't know for sure why Microsoft used C# to implement
ASP.NET Database Result Regions, but I suspect it's
because they were coming from C++ rather than Visual
Basic 6.

>I would have liked to learn the basics of asp.net
>programming by following what FP does (like I have with
>HTML) but I now think it would be easier to knuckle down
>and learn it myself.

Not a good idea. Like most code generators, FrontPage
doesn't create the kind of code a conscientious
programmer would write.

>How can I get FP to write in VB instead of C#. Do, or
>should I, change the page settings to VB.

I don't believe this is possible. (If it is, someone will
now pop up and tell me.)

>Should I do that with any site that has and VB in
>asp.net?

I'm not sure what you mean here.

>Can I write to the database using the Results Wizard or
>other wizard? I was told that FP only reads data through
>the wizard.

You can use INSERT, UPDATE, and DELETE commands in a DRW
custom query. But if you're on the verge of learning to
program, I suggest learning to do this in code rather
than learning to trick the DRW.

>Why and what is <meta name="ProgId"
>content="SharePoint.WebPartPage.Document"> when using
>the asp.net results wizard? Surely, I don't need Share
>Point?

I would say this tag is extraneous. The people who worked
on creating Web Part Pages may have thrown it in for
all .aspx pages, because in their universe .aspx pages
and Web Part Pages are synonymous. In any event, the tag
is harmless.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*

> Not a good idea. Like most code generators, FrontPage
> doesn't create the kind of code a conscientious
> programmer would write.

Actually, Jim, I find the code that FrontPage generates for ASP.Net to be
quite ingenious, unlike its' earlier ASP code. This is probably due to the
fact that ASP.Net is object-oriented, which lends itself well to this sort
of thing. It wouldn't hurt anyone to take a look at how FrontPage does it,
at least for the purpose of "getting their feet wet."

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.


"Jim Buyens" <(E-Mail Removed)> wrote in message
news:0d9d01c3a479$52fa7690$(E-Mail Removed)...
> >-----Original Message-----
> >I have created a database connection (asp.net option)
> >using the results wizard and the page it created is
> >using C# as its default language. It has also created
> >the global.asa and web.config. Why does it have to do
> >this when the asp.net code to connect to a database is
> >so simple (according to my programmer)?
>
> FrontPage stores ASP.NET database connection info in the
> web.config file so that multiple pages can use the same
> connection information. This is also good practice if you
> write your own code.
>
> All ASP.NET applications have a global.asax file.
>
> I don't know for sure why Microsoft used C# to implement
> ASP.NET Database Result Regions, but I suspect it's
> because they were coming from C++ rather than Visual
> Basic 6.
>
> >I would have liked to learn the basics of asp.net
> >programming by following what FP does (like I have with
> >HTML) but I now think it would be easier to knuckle down
> >and learn it myself.
>
> Not a good idea. Like most code generators, FrontPage
> doesn't create the kind of code a conscientious
> programmer would write.
>
> >How can I get FP to write in VB instead of C#. Do, or
> >should I, change the page settings to VB.
>
> I don't believe this is possible. (If it is, someone will
> now pop up and tell me.)
>
> >Should I do that with any site that has and VB in
> >asp.net?
>
> I'm not sure what you mean here.
>
> >Can I write to the database using the Results Wizard or
> >other wizard? I was told that FP only reads data through
> >the wizard.
>
> You can use INSERT, UPDATE, and DELETE commands in a DRW
> custom query. But if you're on the verge of learning to
> program, I suggest learning to do this in code rather
> than learning to trick the DRW.
>
> >Why and what is <meta name="ProgId"
> >content="SharePoint.WebPartPage.Document"> when using
> >the asp.net results wizard? Surely, I don't need Share
> >Point?
>
> I would say this tag is extraneous. The people who worked
> on creating Web Part Pages may have thrown it in for
> all .aspx pages, because in their universe .aspx pages
> and Web Part Pages are synonymous. In any event, the tag
> is harmless.
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *------------------------------------------------------*
> |\----------------------------------------------------/|
> || Microsoft Office FrontPage 2003 Inside Out ||
> || Microsoft FrontPage Version 2002 Inside Out ||
> || Web Database Development Step by Step .NET Edition ||
> || Troubleshooting Microsoft FrontPage 2002 ||
> || Faster Smarter Beginning Programming ||
> || (All from Microsoft Press) ||
> |/----------------------------------------------------\|
> *------------------------------------------------------*
>
>
>

Thanks, answers noted, advice taken


"Jim Buyens" <(E-Mail Removed)> wrote in message
news:0d9d01c3a479$52fa7690$(E-Mail Removed)...
> >-----Original Message-----
> >I have created a database connection (asp.net option)
> >using the results wizard and the page it created is
> >using C# as its default language. It has also created
> >the global.asa and web.config. Why does it have to do
> >this when the asp.net code to connect to a database is
> >so simple (according to my programmer)?
>
> FrontPage stores ASP.NET database connection info in the
> web.config file so that multiple pages can use the same
> connection information. This is also good practice if you
> write your own code.
>
> All ASP.NET applications have a global.asax file.
>
> I don't know for sure why Microsoft used C# to implement
> ASP.NET Database Result Regions, but I suspect it's
> because they were coming from C++ rather than Visual
> Basic 6.
>
> >I would have liked to learn the basics of asp.net
> >programming by following what FP does (like I have with
> >HTML) but I now think it would be easier to knuckle down
> >and learn it myself.
>
> Not a good idea. Like most code generators, FrontPage
> doesn't create the kind of code a conscientious
> programmer would write.
>
> >How can I get FP to write in VB instead of C#. Do, or
> >should I, change the page settings to VB.
>
> I don't believe this is possible. (If it is, someone will
> now pop up and tell me.)
>
> >Should I do that with any site that has and VB in
> >asp.net?
>
> I'm not sure what you mean here.
>
> >Can I write to the database using the Results Wizard or
> >other wizard? I was told that FP only reads data through
> >the wizard.
>
> You can use INSERT, UPDATE, and DELETE commands in a DRW
> custom query. But if you're on the verge of learning to
> program, I suggest learning to do this in code rather
> than learning to trick the DRW.
>
> >Why and what is <meta name="ProgId"
> >content="SharePoint.WebPartPage.Document"> when using
> >the asp.net results wizard? Surely, I don't need Share
> >Point?
>
> I would say this tag is extraneous. The people who worked
> on creating Web Part Pages may have thrown it in for
> all .aspx pages, because in their universe .aspx pages
> and Web Part Pages are synonymous. In any event, the tag
> is harmless.
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *------------------------------------------------------*
> |\----------------------------------------------------/|
> || Microsoft Office FrontPage 2003 Inside Out ||
> || Microsoft FrontPage Version 2002 Inside Out ||
> || Web Database Development Step by Step .NET Edition ||
> || Troubleshooting Microsoft FrontPage 2002 ||
> || Faster Smarter Beginning Programming ||
> || (All from Microsoft Press) ||
> |/----------------------------------------------------\|
> *------------------------------------------------------*
>
>
>

"Kevin Spencer" <(E-Mail Removed)> wrote in message news:<#(E-Mail Removed)>...
> > Not a good idea. Like most code generators, FrontPage
> > doesn't create the kind of code a conscientious
> > programmer would write.
>
> Actually, Jim, I find the code that FrontPage generates for ASP.Net to be
> quite ingenious, unlike its' earlier ASP code. This is probably due to the
> fact that ASP.Net is object-oriented, which lends itself well to this sort
> of thing. It wouldn't hurt anyone to take a look at how FrontPage does it,
> at least for the purpose of "getting their feet wet."

I agree the ASP.NET CODE is better than the ASP code used to be.
However, I've very skeptical of the approach where FrontPage users try
to let FrontPage write 90% of the code and then the user "patches in"
the rest. Although this sometimes works, it seems to me that the
effort is just as much or greater than writing the page from scratch,
and more prone to failure over time.

I must admit, however, that this is a subjective judgment and
ultimately, there's no accounting for taste.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*

> >Should I do that with any site that has and VB in
> >asp.net?
>
> I'm not sure what you mean here.

Page Properties
"Design time control scripting"
'Platform:'
'Server:'
'Client:'
also Site Settings
"Default validation script language"
'Client:'

Do I need to change any of these settings to 'VBScript' / Server ASP when
creating a .net site and using VB as the page language? I thought this was
mainly when using VB script in the pages and so FP would write in VB script
itself when needed.


"Jim Buyens" <(E-Mail Removed)> wrote in message
news:0d9d01c3a479$52fa7690$(E-Mail Removed)...
> >-----Original Message-----
> >I have created a database connection (asp.net option)
> >using the results wizard and the page it created is
> >using C# as its default language. It has also created
> >the global.asa and web.config. Why does it have to do
> >this when the asp.net code to connect to a database is
> >so simple (according to my programmer)?
>
> FrontPage stores ASP.NET database connection info in the
> web.config file so that multiple pages can use the same
> connection information. This is also good practice if you
> write your own code.
>
> All ASP.NET applications have a global.asax file.
>
> I don't know for sure why Microsoft used C# to implement
> ASP.NET Database Result Regions, but I suspect it's
> because they were coming from C++ rather than Visual
> Basic 6.
>
> >I would have liked to learn the basics of asp.net
> >programming by following what FP does (like I have with
> >HTML) but I now think it would be easier to knuckle down
> >and learn it myself.
>
> Not a good idea. Like most code generators, FrontPage
> doesn't create the kind of code a conscientious
> programmer would write.
>
> >How can I get FP to write in VB instead of C#. Do, or
> >should I, change the page settings to VB.
>
> I don't believe this is possible. (If it is, someone will
> now pop up and tell me.)
>
> >Should I do that with any site that has and VB in
> >asp.net?
>
> I'm not sure what you mean here.
>
> >Can I write to the database using the Results Wizard or
> >other wizard? I was told that FP only reads data through
> >the wizard.
>
> You can use INSERT, UPDATE, and DELETE commands in a DRW
> custom query. But if you're on the verge of learning to
> program, I suggest learning to do this in code rather
> than learning to trick the DRW.
>
> >Why and what is <meta name="ProgId"
> >content="SharePoint.WebPartPage.Document"> when using
> >the asp.net results wizard? Surely, I don't need Share
> >Point?
>
> I would say this tag is extraneous. The people who worked
> on creating Web Part Pages may have thrown it in for
> all .aspx pages, because in their universe .aspx pages
> and Web Part Pages are synonymous. In any event, the tag
> is harmless.
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *------------------------------------------------------*
> |\----------------------------------------------------/|
> || Microsoft Office FrontPage 2003 Inside Out ||
> || Microsoft FrontPage Version 2002 Inside Out ||
> || Web Database Development Step by Step .NET Edition ||
> || Troubleshooting Microsoft FrontPage 2002 ||
> || Faster Smarter Beginning Programming ||
> || (All from Microsoft Press) ||
> |/----------------------------------------------------\|
> *------------------------------------------------------*
>
>
>

"Dennis Blondell" <*no spam*(E-Mail Removed)> wrote in message news:<voEqb.5409$(E-Mail Removed)>...
> > >Should I do that with any site that has and VB in
> > >asp.net?
> >
> > I'm not sure what you mean here.
>
> Page Properties
> "Design time control scripting"
> 'Platform:'
> 'Server:'
> 'Client:'
> also Site Settings
> "Default validation script language"
> 'Client:'
>
> Do I need to change any of these settings to 'VBScript' / Server ASP when
> creating a .net site and using VB as the page language? I thought this was
> mainly when using VB script in the pages and so FP would write in VB script
> itself when needed.

I don't believe any of the settings you mention affect ASP.NET pages.

Look, the following ASP.NET code open an Access database, runs a
SELECT statement, and displays the results in tabular form. You just
put this at the top of your Web page

<%@ Page Language="vb" Debug="true" %>
<%@ Import Namespace="System.Data" %>
<%@ Import Namespace="System.Data.OleDb"%>
<script runat="server">
Public Sub Page_Load(sender as Object, e as EventArgs)
Dim conClsf As OleDbConnection
Dim cmdMbrs As OleDbCommand
Dim rdrMbrs As OleDbDataReader
conClsf = New OleDbConnection( _
"Provider=Microsoft.Jet.OLEDB.4.0;" & _
"Data Source=" & server.mappath("classified.mdb") & ";")
conClsf.Open ' Open database connection
cmdMbrs = New OleDbCommand( _
"select * from members order by memberid", _
conClsf) ' Create command object containing SQL statement.
rdrMbrs = cmdMbrs.ExecuteReader ' Use the command object to create a
' data reader
gridMbrs.DataSource = rdrMbrs ' Hook the datagrid to the
datareader.
gridMbrs.DataBind ' Dump the data from the data reader
' into the datagrid.
rdrMbrs.Close ' Cleanup
cmdMbrs.Dispose ' Cleanup
conClsf.Close ' Cleanup
End Sub
</script>

Then, in the body of the Web page, you add this code where you want
the output to appear.

<aspataGrid id="gridMbrs" runat="server" />

From here on, it's all refining SQL statements and formatting the
datagrid.

This stuff really isn't that tough. There's no reason to spend days
figuring how how FrontPage does it (which is, in essence, the same
way).

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*------------------------------------------------------*
|\----------------------------------------------------/|
|| Microsoft Office FrontPage 2003 Inside Out ||
|| Microsoft FrontPage Version 2002 Inside Out ||
|| Web Database Development Step by Step .NET Edition ||
|| Troubleshooting Microsoft FrontPage 2002 ||
|| Faster Smarter Beginning Programming ||
|| (All from Microsoft Press) ||
|/----------------------------------------------------\|
*------------------------------------------------------*

If you are going to use that code, I would not use the native provider. I
would definitly use the managed provider. You will get much better
performance by going straight .NET.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com



"Jim Buyens" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Dennis Blondell" <*no spam*(E-Mail Removed)> wrote in message
news:<voEqb.5409$(E-Mail Removed)>...
> > > >Should I do that with any site that has and VB in
> > > >asp.net?
> > >
> > > I'm not sure what you mean here.
> >
> > Page Properties
> > "Design time control scripting"
> > 'Platform:'
> > 'Server:'
> > 'Client:'
> > also Site Settings
> > "Default validation script language"
> > 'Client:'
> >
> > Do I need to change any of these settings to 'VBScript' / Server ASP
when
> > creating a .net site and using VB as the page language? I thought this
was
> > mainly when using VB script in the pages and so FP would write in VB
script
> > itself when needed.
>
> I don't believe any of the settings you mention affect ASP.NET pages.
>
> Look, the following ASP.NET code open an Access database, runs a
> SELECT statement, and displays the results in tabular form. You just
> put this at the top of your Web page
>
> <%@ Page Language="vb" Debug="true" %>
> <%@ Import Namespace="System.Data" %>
> <%@ Import Namespace="System.Data.OleDb"%>
> <script runat="server">
> Public Sub Page_Load(sender as Object, e as EventArgs)
> Dim conClsf As OleDbConnection
> Dim cmdMbrs As OleDbCommand
> Dim rdrMbrs As OleDbDataReader
> conClsf = New OleDbConnection( _
> "Provider=Microsoft.Jet.OLEDB.4.0;" & _
> "Data Source=" & server.mappath("classified.mdb") & ";")
> conClsf.Open ' Open database connection
> cmdMbrs = New OleDbCommand( _
> "select * from members order by memberid", _
> conClsf) ' Create command object containing SQL statement.
> rdrMbrs = cmdMbrs.ExecuteReader ' Use the command object to create a
> ' data reader
> gridMbrs.DataSource = rdrMbrs ' Hook the datagrid to the
> datareader.
> gridMbrs.DataBind ' Dump the data from the data reader
> ' into the datagrid.
> rdrMbrs.Close ' Cleanup
> cmdMbrs.Dispose ' Cleanup
> conClsf.Close ' Cleanup
> End Sub
> </script>
>
> Then, in the body of the Web page, you add this code where you want
> the output to appear.
>
> <aspataGrid id="gridMbrs" runat="server" />
>
> From here on, it's all refining SQL statements and formatting the
> datagrid.
>
> This stuff really isn't that tough. There's no reason to spend days
> figuring how how FrontPage does it (which is, in essence, the same
> way).
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *------------------------------------------------------*
> |\----------------------------------------------------/|
> || Microsoft Office FrontPage 2003 Inside Out ||
> || Microsoft FrontPage Version 2002 Inside Out ||
> || Web Database Development Step by Step .NET Edition ||
> || Troubleshooting Microsoft FrontPage 2002 ||
> || Faster Smarter Beginning Programming ||
> || (All from Microsoft Press) ||
> |/----------------------------------------------------\|
> *------------------------------------------------------*

I take it back. You have to use oledb 4.0 as Jim did with Access. Dang
Access.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com



"Jim Buyens" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> "Dennis Blondell" <*no spam*(E-Mail Removed)> wrote in message
news:<voEqb.5409$(E-Mail Removed)>...
> > > >Should I do that with any site that has and VB in
> > > >asp.net?
> > >
> > > I'm not sure what you mean here.
> >
> > Page Properties
> > "Design time control scripting"
> > 'Platform:'
> > 'Server:'
> > 'Client:'
> > also Site Settings
> > "Default validation script language"
> > 'Client:'
> >
> > Do I need to change any of these settings to 'VBScript' / Server ASP
when
> > creating a .net site and using VB as the page language? I thought this
was
> > mainly when using VB script in the pages and so FP would write in VB
script
> > itself when needed.
>
> I don't believe any of the settings you mention affect ASP.NET pages.
>
> Look, the following ASP.NET code open an Access database, runs a
> SELECT statement, and displays the results in tabular form. You just
> put this at the top of your Web page
>
> <%@ Page Language="vb" Debug="true" %>
> <%@ Import Namespace="System.Data" %>
> <%@ Import Namespace="System.Data.OleDb"%>
> <script runat="server">
> Public Sub Page_Load(sender as Object, e as EventArgs)
> Dim conClsf As OleDbConnection
> Dim cmdMbrs As OleDbCommand
> Dim rdrMbrs As OleDbDataReader
> conClsf = New OleDbConnection( _
> "Provider=Microsoft.Jet.OLEDB.4.0;" & _
> "Data Source=" & server.mappath("classified.mdb") & ";")
> conClsf.Open ' Open database connection
> cmdMbrs = New OleDbCommand( _
> "select * from members order by memberid", _
> conClsf) ' Create command object containing SQL statement.
> rdrMbrs = cmdMbrs.ExecuteReader ' Use the command object to create a
> ' data reader
> gridMbrs.DataSource = rdrMbrs ' Hook the datagrid to the
> datareader.
> gridMbrs.DataBind ' Dump the data from the data reader
> ' into the datagrid.
> rdrMbrs.Close ' Cleanup
> cmdMbrs.Dispose ' Cleanup
> conClsf.Close ' Cleanup
> End Sub
> </script>
>
> Then, in the body of the Web page, you add this code where you want
> the output to appear.
>
> <aspataGrid id="gridMbrs" runat="server" />
>
> From here on, it's all refining SQL statements and formatting the
> datagrid.
>
> This stuff really isn't that tough. There's no reason to spend days
> figuring how how FrontPage does it (which is, in essence, the same
> way).
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *------------------------------------------------------*
> |\----------------------------------------------------/|
> || Microsoft Office FrontPage 2003 Inside Out ||
> || Microsoft FrontPage Version 2002 Inside Out ||
> || Web Database Development Step by Step .NET Edition ||
> || Troubleshooting Microsoft FrontPage 2002 ||
> || Faster Smarter Beginning Programming ||
> || (All from Microsoft Press) ||
> |/----------------------------------------------------\|
> *------------------------------------------------------*

Here we go. I knew I had used a managed provider for accessing Access!

http://www.microsoft.com/downloads/d...displaylang=en

It's not included in the .NET Framework version 1.0, but it is available via
download. By using the managed provider, you will get much better
performance.

--
Jim Cheshire
Jimco Add-ins
http://www.jimcoaddins.com
===================================
Co-author of Special Edition
Using Microsoft FrontPage 2003
Order it today!
http://sefp2003.frontpagelink.com



"Jim Cheshire" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> If you are going to use that code, I would not use the native provider. I
> would definitly use the managed provider. You will get much better
> performance by going straight .NET.
>
> --
> Jim Cheshire
> Jimco Add-ins
> http://www.jimcoaddins.com
> ===================================
> Co-author of Special Edition
> Using Microsoft FrontPage 2003
> Order it today!
> http://sefp2003.frontpagelink.com
>
>
>
> "Jim Buyens" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > "Dennis Blondell" <*no spam*(E-Mail Removed)> wrote in message
> news:<voEqb.5409$(E-Mail Removed)>...
> > > > >Should I do that with any site that has and VB in
> > > > >asp.net?
> > > >
> > > > I'm not sure what you mean here.
> > >
> > > Page Properties
> > > "Design time control scripting"
> > > 'Platform:'
> > > 'Server:'
> > > 'Client:'
> > > also Site Settings
> > > "Default validation script language"
> > > 'Client:'
> > >
> > > Do I need to change any of these settings to 'VBScript' / Server ASP
> when
> > > creating a .net site and using VB as the page language? I thought this
> was
> > > mainly when using VB script in the pages and so FP would write in VB
> script
> > > itself when needed.
> >
> > I don't believe any of the settings you mention affect ASP.NET pages.
> >
> > Look, the following ASP.NET code open an Access database, runs a
> > SELECT statement, and displays the results in tabular form. You just
> > put this at the top of your Web page
> >
> > <%@ Page Language="vb" Debug="true" %>
> > <%@ Import Namespace="System.Data" %>
> > <%@ Import Namespace="System.Data.OleDb"%>
> > <script runat="server">
> > Public Sub Page_Load(sender as Object, e as EventArgs)
> > Dim conClsf As OleDbConnection
> > Dim cmdMbrs As OleDbCommand
> > Dim rdrMbrs As OleDbDataReader
> > conClsf = New OleDbConnection( _
> > "Provider=Microsoft.Jet.OLEDB.4.0;" & _
> > "Data Source=" & server.mappath("classified.mdb") & ";")
> > conClsf.Open ' Open database connection
> > cmdMbrs = New OleDbCommand( _
> > "select * from members order by memberid", _
> > conClsf) ' Create command object containing SQL statement.
> > rdrMbrs = cmdMbrs.ExecuteReader ' Use the command object to create a
> > ' data reader
> > gridMbrs.DataSource = rdrMbrs ' Hook the datagrid to the
> > datareader.
> > gridMbrs.DataBind ' Dump the data from the data reader
> > ' into the datagrid.
> > rdrMbrs.Close ' Cleanup
> > cmdMbrs.Dispose ' Cleanup
> > conClsf.Close ' Cleanup
> > End Sub
> > </script>
> >
> > Then, in the body of the Web page, you add this code where you want
> > the output to appear.
> >
> > <aspataGrid id="gridMbrs" runat="server" />
> >
> > From here on, it's all refining SQL statements and formatting the
> > datagrid.
> >
> > This stuff really isn't that tough. There's no reason to spend days
> > figuring how how FrontPage does it (which is, in essence, the same
> > way).
> >
> > Jim Buyens
> > Microsoft FrontPage MVP
> > http://www.interlacken.com
> > Author of:
> > *------------------------------------------------------*
> > |\----------------------------------------------------/|
> > || Microsoft Office FrontPage 2003 Inside Out ||
> > || Microsoft FrontPage Version 2002 Inside Out ||
> > || Web Database Development Step by Step .NET Edition ||
> > || Troubleshooting Microsoft FrontPage 2002 ||
> > || Faster Smarter Beginning Programming ||
> > || (All from Microsoft Press) ||
> > |/----------------------------------------------------\|
> > *------------------------------------------------------*
>
>