ASP errors

[David Jacobus]

Since upgrading to Windows 2003 Server from Windows 2000
Enterprise Server we have had alot of ASP problems. The
problems are centered around asp pages which are one level
or more below the main folder within a web site. We have
many web sites which have used the database interface
wizard in FrontPage which puts these pages up to three
levels deep inside the folder hierarchy of the main site.
The pages will not work with IIS 6. I have had to re-
engineer many of these sites without the database
interface wizard. My solution at this point is to put all
ASP pages at the root level which seems to work but
negates all version of Frontpage management including
FrontPage 2003 Beta. This is a serious problem!
Especially for us who teach FrontPage and ASP!

[Ray at]

What errors?

Drop Frontpage man!

Ray at work

"David Jacobus" <davidjacobus@hotmail.com> wrote in message
news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...

> Since upgrading to Windows 2003 Server from Windows 2000
> Enterprise Server we have had alot of ASP problems. The
> problems are centered around asp pages which are one level
> or more below the main folder within a web site. We have
> many web sites which have used the database interface
> wizard in FrontPage which puts these pages up to three
> levels deep inside the folder hierarchy of the main site.
> The pages will not work with IIS 6. I have had to re-
> engineer many of these sites without the database
> interface wizard. My solution at this point is to put all
> ASP pages at the root level which seems to work but
> negates all version of Frontpage management including
> FrontPage 2003 Beta. This is a serious problem!
> Especially for us who teach FrontPage and ASP!

[David Jacobus]

HTTP 500 - Internal Server Error

>-----Original Message-----
>What errors?
>
>Drop Frontpage man!
>
>Ray at work
>
>"David Jacobus" <davidjacobus@hotmail.com> wrote in

message

>news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...

>> Since upgrading to Windows 2003 Server from Windows 2000
>> Enterprise Server we have had alot of ASP problems. The
>> problems are centered around asp pages which are one

level

>> or more below the main folder within a web site. We

have

>> many web sites which have used the database interface
>> wizard in FrontPage which puts these pages up to three
>> levels deep inside the folder hierarchy of the main

site.

>> The pages will not work with IIS 6. I have had to re-
>> engineer many of these sites without the database
>> interface wizard. My solution at this point is to put

all

>> ASP pages at the root level which seems to work but
>> negates all version of Frontpage management including
>> FrontPage 2003 Beta. This is a serious problem!
>> Especially for us who teach FrontPage and ASP!

>
>
>.
>

[Ray at]

[url]http://www.aspfaq.com/2109[/url]

Ray at work

"David Jacobus" <davidjacobus@hotmail.com> wrote in message
news:05fd01c37bca$cc6a3ab0$a101280a@phx.gbl...

> HTTP 500 - Internal Server Error

> >-----Original Message-----
> >What errors?
> >
> >Drop Frontpage man!
> >
> >Ray at work
> >
> >"David Jacobus" <davidjacobus@hotmail.com> wrote in

> message

> >news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...

> >> Since upgrading to Windows 2003 Server from Windows 2000
> >> Enterprise Server we have had alot of ASP problems. The
> >> problems are centered around asp pages which are one

> level

> >> or more below the main folder within a web site. We

> have

> >> many web sites which have used the database interface
> >> wizard in FrontPage which puts these pages up to three
> >> levels deep inside the folder hierarchy of the main

> site.

> >> The pages will not work with IIS 6. I have had to re-
> >> engineer many of these sites without the database
> >> interface wizard. My solution at this point is to put

> all

> >> ASP pages at the root level which seems to work but
> >> negates all version of Frontpage management including
> >> FrontPage 2003 Beta. This is a serious problem!
> >> Especially for us who teach FrontPage and ASP!

> >
> >
> >.
> >

[Tom B]

I think since he's teaching it, he can't really drop it.

Now I'm not familiar with Frontpage or even Win2003, but I believe there's a
setting in 2003 that is on by default (off by default in 2000) for
references to Parent directories.
If Frontpage is anything like interdev, then by default it references files
in a goofy manner. Often, I'll get things like
"../../Home/something/Default.asp" which is really in the same folder I'm
already in (up two down two), which I'm sure would cause a problem in 2003.



"Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...

> What errors?
>
> Drop Frontpage man!
>
> Ray at work
>
> "David Jacobus" <davidjacobus@hotmail.com> wrote in message
> news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...

> > Since upgrading to Windows 2003 Server from Windows 2000
> > Enterprise Server we have had alot of ASP problems. The
> > problems are centered around asp pages which are one level
> > or more below the main folder within a web site. We have
> > many web sites which have used the database interface
> > wizard in FrontPage which puts these pages up to three
> > levels deep inside the folder hierarchy of the main site.
> > The pages will not work with IIS 6. I have had to re-
> > engineer many of these sites without the database
> > interface wizard. My solution at this point is to put all
> > ASP pages at the root level which seems to work but
> > negates all version of Frontpage management including
> > FrontPage 2003 Beta. This is a serious problem!
> > Especially for us who teach FrontPage and ASP!

>
>

[Tom B]

[url]http://support.microsoft.com/default.aspx?scid=kb;en-us;332117[/url]


"Tom B" <shuckle@hotmail.com> wrote in message
news:%23yyhJ38eDHA.2352@TK2MSFTNGP09.phx.gbl...

> I think since he's teaching it, he can't really drop it.
>
> Now I'm not familiar with Frontpage or even Win2003, but I believe there's

a

> setting in 2003 that is on by default (off by default in 2000) for
> references to Parent directories.
> If Frontpage is anything like interdev, then by default it references

files

> in a goofy manner. Often, I'll get things like
> "../../Home/something/Default.asp" which is really in the same folder I'm
> already in (up two down two), which I'm sure would cause a problem in

2003.

>
>
>
> "Ray at <%=sLocation%>" <myfirstname at lane34 dot com> wrote in message
> news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...

> > What errors?
> >
> > Drop Frontpage man!
> >
> > Ray at work
> >
> > "David Jacobus" <davidjacobus@hotmail.com> wrote in message
> > news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...

> > > Since upgrading to Windows 2003 Server from Windows 2000
> > > Enterprise Server we have had alot of ASP problems. The
> > > problems are centered around asp pages which are one level
> > > or more below the main folder within a web site. We have
> > > many web sites which have used the database interface
> > > wizard in FrontPage which puts these pages up to three
> > > levels deep inside the folder hierarchy of the main site.
> > > The pages will not work with IIS 6. I have had to re-
> > > engineer many of these sites without the database
> > > interface wizard. My solution at this point is to put all
> > > ASP pages at the root level which seems to work but
> > > negates all version of Frontpage management including
> > > FrontPage 2003 Beta. This is a serious problem!
> > > Especially for us who teach FrontPage and ASP!

> >
> >

>
>

[David Jacobus]

WOW! Thanks so much for helping us with this problem, we
are in business now. Again Thanks

>-----Original Message-----
>[url]http://support.microsoft.com/default.aspx?scid=kb;en-[/url]

us;332117

>
>
>"Tom B" <shuckle@hotmail.com> wrote in message
>news:%23yyhJ38eDHA.2352@TK2MSFTNGP09.phx.gbl...

>> I think since he's teaching it, he can't really drop it.
>>
>> Now I'm not familiar with Frontpage or even Win2003,

but I believe there's

>a

>> setting in 2003 that is on by default (off by default

in 2000) for

>> references to Parent directories.
>> If Frontpage is anything like interdev, then by default

it references

>files

>> in a goofy manner. Often, I'll get things like
>> "../../Home/something/Default.asp" which is really in

the same folder I'm

>> already in (up two down two), which I'm sure would

cause a problem in

>2003.

>>
>>
>>
>> "Ray at <%=sLocation%>" <myfirstname at lane34 dot com>

wrote in message

>> news:ODM7jk8eDHA.2328@TK2MSFTNGP09.phx.gbl...

>> > What errors?
>> >
>> > Drop Frontpage man!
>> >
>> > Ray at work
>> >
>> > "David Jacobus" <davidjacobus@hotmail.com> wrote in

message

>> > news:05d701c37bc8$9c8a2280$a101280a@phx.gbl...
>> > > Since upgrading to Windows 2003 Server from Windows

2000

>> > > Enterprise Server we have had alot of ASP

problems. The

>> > > problems are centered around asp pages which are

one level

>> > > or more below the main folder within a web site.

We have

>> > > many web sites which have used the database

interface

>> > > wizard in FrontPage which puts these pages up to

three

>> > > levels deep inside the folder hierarchy of the main

site.

>> > > The pages will not work with IIS 6. I have had to

re-

>> > > engineer many of these sites without the database
>> > > interface wizard. My solution at this point is to

put all

>> > > ASP pages at the root level which seems to work but
>> > > negates all version of Frontpage management

including

>> > > FrontPage 2003 Beta. This is a serious problem!
>> > > Especially for us who teach FrontPage and ASP!
>> >
>> >

>>
>>

>
>
>.
>

[McKirahan]

"Sean" <S.Cairns@belfasttelegraph.co.uk> wrote in message
news:6D9B2927-73FB-4082-A346-59BD56D41552@microsoft.com...

> Could someone please help me fix up the below code:
>
> Ive been getting the following error message:
>
> (Microsoft VBScript runtime error '800a01f4'
> Variable is undefined: 'adCmdStoredProc'
> /testing.asp, line 23 )

[snip]


You previously posted your questions as "ASP still having problems"!
Your answer was posted there by Aaron: "include adovbs.inc".

This is done by inserting the following line at the top of your script:
<!-- #include file="adovbs.inc" -->

All of the " ad" prefixed elements are constants that are declared in
"adovbs.inc".

Alternatively, you could just include the ones you reference:

Const adCmdStoredProc = &H0004
Const adDate = 7
Const adParamInput = &H0001