Dear All,

Many thanks for all your help with putting together my few simple ASP
pages. They now all work... or so I thought. I have written all the scrips
in J(ava)Script.

I recently moved the pages to an intranet site and made several very
interesting discoveries.

1). Using PWS that came with FrontPage '98 (awful) the relative links style
sheets do not seem to work. However, images, scripts and includes in
directories parallel to the style directory are found without a hitch. 

2). The buttons that I have on a form to allow the user to search the
database do not display in IE5.5. This does not seem to be a nesting error
as the form's elements are all enclosed within one table cell.

3). Communicator 4.7 does not seem to like any of the search form though
the form does appear in MSIE from version 4 on.

4). NN 6 and PR7 display all the bits in all their glory and work nicely, I
assume the MSIE 6 will be similarly good.

Has anybody come across this kind of behaviour before.

Oh yes, it's well-known.  Every book I have on scripting or html
mentions the differences between the browsers.  ASP is going to work the
same in every browser, as long as it is processed on the server.  Once
you start writing script or html that processes on the client, you are
going to run into all sorts of differences from one browser to the next.
I have web pages that determine what kind of browser you are using and
then redirect you to a set of pages written for that type of browser.
However, when a new browser gets released, like Mozilla
(www.mozilla.org), those pages have to be rewritten.

Carl Olsen, MCSE

> -----Original Message-----
> From: Dr John Donovan [mailto:jdonovan@i...]
> Sent: Tuesday, July 30, 2002 10:44 AM
> To: Access ASP
> Subject: [access_asp] ASP Pages in Netscape Communiccator
> 
> Dear All,
> 
> Many thanks for all your help with putting together my few simple ASP
> pages. They now all work... or so I thought. I have written all the
scrips
> in J(ava)Script.
> 
> I recently moved the pages to an intranet site and made several very
> interesting discoveries.
> 
> 1). Using PWS that came with FrontPage '98 (awful) the relative links
> style
> sheets do not seem to work. However, images, scripts and includes in
> directories parallel to the style directory are found without a hitch.
> 
> 2). The buttons that I have on a form to allow the user to search the
> database do not display in IE5.5. This does not seem to be a nesting
error
> as the form's elements are all enclosed within one table cell.
> 
> 3). Communicator 4.7 does not seem to like any of the search form
though
> the form does appear in MSIE from version 4 on.
> 
> 4). NN 6 and PR7 display all the bits in all their glory and work
nicely,
> I
> assume the MSIE 6 will be similarly good.
> 
> Has anybody come across this kind of behaviour before.
> to unsubscribe send a blank email to leave-access_asp-
> 1112135Q@p...

ns4 is very strict on form elements, especially dynamically driven popup
menus - they wont work unless they're in a form tag, regardless of how your
using them.

ns4 is such a pain!!!

jake

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
From: "jake williamson 28" <jake.williamson@2...>
Subject: [access_asp] RE: ASP Pages in Netscape Communiccator


: ns4 is very strict on form elements, especially dynamically driven popup
: menus - they wont work unless they're in a form tag, regardless of how
your
: using them.
:
: ns4 is such a pain!!!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

...maybe if programmers actually were aware of the HTML specifications, and
followed them, it wouldn't be so painful.

Placing form elements outside <form></form> tags will not validate under any
HTML DocType:

Try it and see:
http://validator.w3.org/

Cheers
Ken

Dear All,

Since I last posted about some odd behaviours in different browsers I have
made some interesting discoveries.
1). Apparently under PWS (FrontPage '98 - will change very shortly) you
have to give every sub directory of the home directory a virtual identity.
2). For no apparent reason NN4 has decided to co-operate but still refuses
a pointer to an off-page style sheet.
3). And, most bizarrely of all, MSIE 5.5 has discovered "submit buttons"
where it thought none existed before.

While I am here, one of the slots on my form allows people to enter a name.
Irish names can have "O'" in front of them (e.g. O'Brien, O'Neill -the O'
means the same as "von" in German or "de" in French names). However, the
correct English spelling of an "O'" name is O' (O apostrophe). Of course
unaccompanied apostrophes are to be frowned upon.

I thought of switching the text slot to a text area (the string can be
manipulated) but there has to be a simpler way of doing things.

> Dear All,

> Many thanks for all your help with putting together my few simple ASP
p> ages. They now all work... or so I thought. I have written all the scrips
i> n J(ava)Script.

> I recently moved the pages to an intranet site and made several very
i> nteresting discoveries.

> 1). Using PWS that came with FrontPage '98 (awful) the relative links style
s> heets do not seem to work. However, images, scripts and includes in
d> irectories parallel to the style directory are found without a hitch. 

> 2). The buttons that I have on a form to allow the user to search the
d> atabase do not display in IE5.5. This does not seem to be a nesting error
a> s the form's elements are all enclosed within one table cell.

> 3). Communicator 4.7 does not seem to like any of the search form though
t> he form does appear in MSIE from version 4 on.

> 4). NN 6 and PR7 display all the bits in all their glory and work nicely, I
a> ssume the MSIE 6 will be similarly good.

> Has anybody come across this kind of behaviour before.