Does Macintosh read uppercase?

[Jim Fitzgerald]

Does Macintosh read upper and lower case scripts? I have a form that uses
JavaScript to manipulate several fields. The field names are mixed upper and
lowercase.

Could that cause a Mac to ignore the scripts?

 

[Murray]

No.

 

[Murray]

Errr -

Yes. No.

 

[Jim Fitzgerald]

Thanks Murry:

I appreciate your taking the time to reply.

Macs seem to be reading the fields ok and most web Bots, but the javascript
calculations and validations it seems to ignore. I am guessing that I will
have to rename the fields and their references in the javascript to all
lowercase and underscores.

Do you think that will solve the problem, or will it take some major changes
to make it work? I can make the case-changes but I am not a programmer, but
my son, who did the form for me is.

 

[Murray]

Macs seem to be reading the fields ok and most web Bots, but the

javascript
calculations and validations it seems to ignore. I am guessing that I
will
have to rename the fields and their references in the javascript to all
lowercase and underscores.

I doubt that is the problem. I think it's much more likely that the
scripting itself is overlooking something "Macintoshy".

While I am not much of a scripter, others here are - you wanna post the
code, or a link to the page? If the latter, then I can examine it "in
Macinto" so to speak....

 

[Jim Carlock]

Javascript is supposed to be case-sensitive on all platforms,
(as is Java). Other scripting languages like vbScript and ASP
don't have this problem.

If you have variables named:

var Idx = 1;
var idx = 10;

they are two DIFFERENT variables.

There are a couple things that you might want to consider
before jumping to conclusions, though...

1) Does it happen on ALL MacIntosh computers? If it
works on one but not on another, then there is something
wrong or different about the Mac that it doesn't work on.
This is probably the most important aspect to identify.
2) Look at the website with different browsers. Does it
appear to be a problem when using the mozilla or firefox
browser? If it fails on mozilla or firefox but runs on IE,
then all of the code should be rewritten so that it runs on
the mozilla browsers as well as Internet Explorer. The
mozilla and firefox browsers are free and easy to install...
http://www.mozilla.org/products/firefox/

What's the webpage that's having the problem??? Maybe
someone here has a Mac or can test the page with a
Mozilla browser if you don't want to do it yourself.

--
Jim Carlock
Post replies to newsgroup.

Macs seem to be reading the fields ok and most web Bots, but the
javascript
calculations and validations it seems to ignore. I am guessing that I
will
have to rename the fields and their references in the javascript to all
lowercase and underscores.

I doubt that is the problem. I think it's much more likely that the
scripting itself is overlooking something "Macintoshy".

While I am not much of a scripter, others here are - you wanna post the
code, or a link to the page? If the latter, then I can examine it "in
Macinto" so to speak....

 

[Jim Fitzgerald]

To Murray & Jim:

Thanks for taking the time to consider this. As you say, it may be a very
simple thing. I will get it posted on a dummy site so that you can look at
it without affecting my regular database.

 

[Murray]

Jim:

That's the best idea....

 

[Jim Fitzgerald]

Jim: I have the web pages on a web server now, so you can look at them
through any browser. You can't hurt it.

Here is what you should do. Open this page. The page has two forms one one
page. It loads pre-existing district numbers and club names, and then
redirects that information to a third form on a seperate page, which should
open automatically. It will in IE, so you will want to run it in IE to see
how the scripts are supposed to run.
http://www.rotary5830.org/Registrations/2005/pe.asp

Most of the problems show up on the third (last) form.

Thanks for any help you can give. This is so frustrating because it works
so well on 95% of the registrations.

 

[Jim Fitzgerald]

Jim:

I have the web pages on a web server now, so you can look at them
through any browser. You can't hurt it.

Here is what you should do. Open this page. The page has two forms one one
page. It loads pre-existing district numbers and club names, and then
redirects that information to a third form on a seperate page, which should
open automatically. It will in IE, so you will want to run it in IE to see
how the scripts are supposed to run.
http://www.rotary5830.org/Registrations/2005/pe.asp

Most of the problems show up on the third (last) form.

Thanks for any help you can give. This is so frustrating because it works
so well on 95% of the registrations.

 

[Jim Fitzgerald]

Murray:
I have the web pages on a web server now, so you can look at them through
any browser. You can't hurt it.

Here is what you should do. Open this page. The page has two forms one one
page. It loads pre-existing district numbers and club names, and then
redirects that information to a third form on a seperate page, which should
open automatically. It will in IE, so you will want to run it in IE to see
how the scripts are supposed to run.
http://www.rotary5830.org/Registrations/2005/pe.asp

Most of the problems show up on the third (last) form.

Thanks for any help you can give. This is so frustrating because it works
so well on 95% of the registrations.

 

[Murray]

Using OSX (Panther), I was able to successfully navigate to the third form
with FF1/Safari 1.2.4/IE5.2x.

The only thing I saw was a secure form alert from IE5 each time I selected
something from the first two forms.

Seems to work OK for me.

 

[Jim Carlock]

It looks like your error trapping isn't working:

Microsoft JET Database Engine error '80040e14'
Syntax error (missing operator) in query expression 'PetsReg.ID ='.
/Registrations/authorizenet2/PEConfirmCC.asp, line 45

That's what I get when I click on the Submit button without
filling any information in.

--
Jim Carlock
Post replies to newsgroup.

Jim:

I have the web pages on a web server now, so you can look at them
through any browser. You can't hurt it.

Here is what you should do. Open this page. The page has two forms one one
page. It loads pre-existing district numbers and club names, and then
redirects that information to a third form on a seperate page, which should
open automatically. It will in IE, so you will want to run it in IE to see
how the scripts are supposed to run.
http://www.rotary5830.org/Registrations/2005/pe.asp

Most of the problems show up on the third (last) form.

Thanks for any help you can give. This is so frustrating because it works
so well on 95% of the registrations.

 

[Murray]

Yeah - I saw that, too, and I had filled in the whole form, so, it's
something else I think....

 

[Jim Carlock]

There doesn't seem to be any error trapping in <% asp %>
code, I can get to the third page, but it's on the third page
that I get the database error, which looks like the .asp code
isn't set up to trap errors and gracefully handle those server
side errors.

The javascript interaction with .asp code is handling the
creation of the listboxes nicely enough.

If the browser doesn't allow javascript, they'll never get
the second listbox. The case of the page name changes.
It starts out as pe.asp, then once something is selected
in the listbox, it changes to PE.ASP. I don't know if that
will be a problem to the javascript... but it's something
worth knowing maybe.

So those are my two best guesses. 1) Error trapping on
the server side, 2) and the page name changing from lcase
to ucase... <shrug>

--
Jim Carlock
Post replies to newsgroup.

Yeah - I saw that, too, and I had filled in the whole form, so, it's
something else I think....

 

[Murray]

The casing means that an entirely new page is reloading most likely, but
that would not cause a problem on the Mac - only on the server side of
things.

As I understood the original question, the problem was getting to the 3rd
form at all, on a Mac, which you and I were both able to do. However, as
you say, this method is completely vulnerable to no-javascript. At the
least, the page should have a <noscript></noscript> warning that it will be
non-functional (as you would see on my site at http://www.reedfax.com when
you disable js.

 

[Jim Fitzgerald]

Again, thank you both for working on my problem.

I think i may not have explained it correctly. The problem is not in
passing the 1st and second forms data to the third form on the next page, but
rather what happens when the data gets to the peregform.asp page.

The page pe.asp has two forms, Form1 & Form2, which collect the district
number and club name and pass it on to the third page peregform.asp. Since i
don't have access to a Mac browser I have to guess at this, but I think that
part works fine, since it is server-side scripting. At least it works in all
cases where the Browser security is not set to "High".

The problems on the peregform.asp page are these:

1. when someone chooses one of the first set of options, the correct amount
for that option does not appear in the window. It should be either $250.00,
or $240.00, or $190.00, depending on whether you pick the 1st, 2nd, or 3rd
option. Additionally, if the 1st option is not chosen, then all of the
fields in the President-Elects section should be disabled, but that is not
being done on Mac browsers.

The same is true of the second set of options. The amount does not show in
the window here either. It should be $0.00 if the spouse is not registering,
or is registering seperately, and it should be $190.0 if the spouse is being
registered.

If the spouse is not being registered, the fields that collect his or her
name and club information are supposed to be disabled. Again this is not
being done on the MAcs.

The club and district number do not appear in the database on the Macs either.

Finally the Total registration which is derived from option 1 & 2 is not
being calculated at all.

In some netscape browsers the district and club appear correctly on the
form, but do not get posted to the database.

Would you please fill out the forms and submit them usine IE. and then do
the same thing with OSX and submit it.

You can then look at the results at:
http://www.rotary5830.org/Registrations/Bill/Reports/AllByDate.asp

Thanks again,

 

[Jim Carlock]

The following code should update textboxes on all browsers that
support javascript. I've run into problems in the past trying to
get collections of objects to work...


<head>
<script type="text/javascript"><!-- //Hide from older browsers
var lngSelectedGood = -1;
var lngUnitPrice = 0;
var lngQty = 0;
var lngTotal = 0;
function fClearForm(form) {
form.txtUnitPrice.value = "";
form.txtQty.value = "";
form.txtTotalPrice.value = "";
return;
}
function fGoodSelected(form) {
var strTemp = "Blah!";
//var coll = document.all.tags("SELECT"); //PROBLEM SOME BROWSERS
fClearForm(form);
//strTemp = coll(0).options[lngSelectedGood].text; // this works but not used anymore
lngSelectedGood = parseInt(form.cmbSelectedGood.selectedIndex);
//we are opting to to identify by using document.FORMNAME.objectname
strTemp = document.Calculator.cmbSelectedGood.options[lngSelectedGood].text;
// if you had a text box to display what was selected...
form.txtSelectedGood.value = strTemp;
fCalculate(form);
}
function fCalculate(form) {
// someone types in a number
lngUnitPrice = parseInt(form.txtUnitPrice.value);
lngQty = parseInt(form.txtQty.value);
lngTotal = lngUnitPrice * lngQty;
return(lngTotal);
}
function fUpdateSCTFields(form) {
//an array holds info loaded up from a database
form.txtUnitPrice.value = parseInt(Goods[lngSelectedGood][0]);
form.txtShippingCost.value = parseInt(Goods[lngSelectedGood][1]);
return;
}
--></script>
</head>
<body>
<form name="Calculator">
<!-- The nice thing about combo boxes/list boxes denoted by
The first item in the collection of <select> objects is this one...
-->
<select name="cmbSelectedGood" tabindex="0" onchange="fGoodSelected(this.form)">
<option selected>Good #1</option>
.... more options / asp script to load up from db...
</select>
<input type="text" name="txtQty" size="5" value="0"
tabindex="1" MAXLENGTH="3"
onchange="fQtyChanged(this.form)" /><br />
<input type="text" name="txtUnitPrice" size="10" tabindex="12" disabled />
</form>

If you watch the flow of the code, I have one calculate function,
and the onchange="" items inside the combo boxes (or
listboxes) call functions to update disabled txtboxes <input> and
in the end call the fCalculate(form) function to calculate. I
shortened most of this code, but passing the form into the
functions works very well, function0001(this.form).

Also refering to document.FormName.objectName is a great
easy way to reference the objects. But you'll need to tag each
object with a name... (name="txtPrice"). The document is the
global tag in JavaScript used to reference the whole HTML
document. There is a form declaration (NOTE: the name is
case sensitive in all browsers when referencing it in JavaScript).
The Form Name is very important for all javascript code.

I've ran into some problems with javascript collections in the
past not working on NetScape browsers. That was a couple
years ago.

Hope that helps.

--
Jim Carlock
Post replies to newsgroup.

Again, thank you both for working on my problem.

I think i may not have explained it correctly. The problem is not in
passing the 1st and second forms data to the third form on the next page, but
rather what happens when the data gets to the peregform.asp page.

The page pe.asp has two forms, Form1 & Form2, which collect the district
number and club name and pass it on to the third page peregform.asp. Since i
don't have access to a Mac browser I have to guess at this, but I think that
part works fine, since it is server-side scripting. At least it works in all
cases where the Browser security is not set to "High".

The problems on the peregform.asp page are these:

1. when someone chooses one of the first set of options, the correct amount
for that option does not appear in the window. It should be either $250.00,
or $240.00, or $190.00, depending on whether you pick the 1st, 2nd, or 3rd
option. Additionally, if the 1st option is not chosen, then all of the
fields in the President-Elects section should be disabled, but that is not
being done on Mac browsers.

The same is true of the second set of options. The amount does not show in
the window here either. It should be $0.00 if the spouse is not registering,
or is registering seperately, and it should be $190.0 if the spouse is being
registered.

If the spouse is not being registered, the fields that collect his or her
name and club information are supposed to be disabled. Again this is not
being done on the MAcs.

The club and district number do not appear in the database on the Macs either.

Finally the Total registration which is derived from option 1 & 2 is not
being calculated at all.

In some netscape browsers the district and club appear correctly on the
form, but do not get posted to the database.

Would you please fill out the forms and submit them usine IE. and then do
the same thing with OSX and submit it.

You can then look at the results at:
http://www.rotary5830.org/Registrations/Bill/Reports/AllByDate.asp

Thanks again,

 

[Jim Fitzgerald]

Thanks Jim, This will take a while to digest and implement. I do appreciate
your time and help.

The following code should update textboxes on all browsers that
support javascript. I've run into problems in the past trying to
get collections of objects to work...


<head>
<script type="text/javascript"><!-- //Hide from older browsers
var lngSelectedGood = -1;
var lngUnitPrice = 0;
var lngQty = 0;
var lngTotal = 0;
function fClearForm(form) {
form.txtUnitPrice.value = "";
form.txtQty.value = "";
form.txtTotalPrice.value = "";
return;
}
function fGoodSelected(form) {
var strTemp = "Blah!";
//var coll = document.all.tags("SELECT"); //PROBLEM SOME BROWSERS
fClearForm(form);
//strTemp = coll(0).options[lngSelectedGood].text; // this works but not used anymore
lngSelectedGood = parseInt(form.cmbSelectedGood.selectedIndex);
//we are opting to to identify by using document.FORMNAME.objectname
strTemp = document.Calculator.cmbSelectedGood.options[lngSelectedGood].text;
// if you had a text box to display what was selected...
form.txtSelectedGood.value = strTemp;
fCalculate(form);
}
function fCalculate(form) {
// someone types in a number
lngUnitPrice = parseInt(form.txtUnitPrice.value);
lngQty = parseInt(form.txtQty.value);
lngTotal = lngUnitPrice * lngQty;
return(lngTotal);
}
function fUpdateSCTFields(form) {
//an array holds info loaded up from a database
form.txtUnitPrice.value = parseInt(Goods[lngSelectedGood][0]);
form.txtShippingCost.value = parseInt(Goods[lngSelectedGood][1]);
return;
}
--></script>
</head>
<body>
<form name="Calculator">
<!-- The nice thing about combo boxes/list boxes denoted by
The first item in the collection of <select> objects is this one...
-->
<select name="cmbSelectedGood" tabindex="0" onchange="fGoodSelected(this.form)">
<option selected>Good #1</option>
.... more options / asp script to load up from db...
</select>
<input type="text" name="txtQty" size="5" value="0"
tabindex="1" MAXLENGTH="3"
onchange="fQtyChanged(this.form)" /><br />
<input type="text" name="txtUnitPrice" size="10" tabindex="12" disabled />
</form>

If you watch the flow of the code, I have one calculate function,
and the onchange="" items inside the combo boxes (or
listboxes) call functions to update disabled txtboxes <input> and
in the end call the fCalculate(form) function to calculate. I
shortened most of this code, but passing the form into the
functions works very well, function0001(this.form).

Also refering to document.FormName.objectName is a great
easy way to reference the objects. But you'll need to tag each
object with a name... (name="txtPrice"). The document is the
global tag in JavaScript used to reference the whole HTML
document. There is a form declaration (NOTE: the name is
case sensitive in all browsers when referencing it in JavaScript).
The Form Name is very important for all javascript code.

I've ran into some problems with javascript collections in the
past not working on NetScape browsers. That was a couple
years ago.

Hope that helps.

--
Jim Carlock
Post replies to newsgroup.

Again, thank you both for working on my problem.

I think i may not have explained it correctly. The problem is not in
passing the 1st and second forms data to the third form on the next page, but
rather what happens when the data gets to the peregform.asp page.

The page pe.asp has two forms, Form1 & Form2, which collect the district
number and club name and pass it on to the third page peregform.asp. Since i
don't have access to a Mac browser I have to guess at this, but I think that
part works fine, since it is server-side scripting. At least it works in all
cases where the Browser security is not set to "High".

The problems on the peregform.asp page are these:

1. when someone chooses one of the first set of options, the correct amount
for that option does not appear in the window. It should be either $250.00,
or $240.00, or $190.00, depending on whether you pick the 1st, 2nd, or 3rd
option. Additionally, if the 1st option is not chosen, then all of the
fields in the President-Elects section should be disabled, but that is not
being done on Mac browsers.

The same is true of the second set of options. The amount does not show in
the window here either. It should be $0.00 if the spouse is not registering,
or is registering seperately, and it should be $190.0 if the spouse is being
registered.

If the spouse is not being registered, the fields that collect his or her
name and club information are supposed to be disabled. Again this is not
being done on the MAcs.

The club and district number do not appear in the database on the Macs either.

Finally the Total registration which is derived from option 1 & 2 is not
being calculated at all.

In some netscape browsers the district and club appear correctly on the
form, but do not get posted to the database.

Would you please fill out the forms and submit them usine IE. and then do
the same thing with OSX and submit it.

You can then look at the results at:
http://www.rotary5830.org/Registrations/Bill/Reports/AllByDate.asp

Thanks again,

 

[Jim Carlock]

Oh, here's a great link:
http://www.w3schools.com/js/js_guidelines.asp

Also, check out this link, as it can help... Click on the
some of the examples and mess with the code there.
http://www.w3schools.com/js/js_examples.asp

The HTML object names are case-sensitive inside of JavaScript
on browsers. I have some code that is configured to demonstrate
this. I ran some tests and commented it heavily. The code below
is fully functional and you can copy it to your website or your disk
and view it and mess with it without having to send it to a server.
Just copy and paste it into an a blank document called test.htm,
watch that first <!DOCTYPE line though, my Outlook Express
might take some quotes out. If...
http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
is not quoted below, put some quotes around it "".

HTH.

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>JavaScript Case Sensitivity</title>
<meta name="Author" content="MicroCosmoTalk" />
<meta name="Copyright" content="Copyright 2004. All rights reserved." />
<meta name="Description" content="Description" />
<meta name="Generator" content="MicroCosmoTalk HDT" />
<meta name="Keywords" content="key, words" />
<meta name="Language" content="en-us" />
<!--
<script language="JavaScript" type="text/javascript" src="js.js"></script>
-->
<script language="JavaScript" type="text/javascript"><!-- Hide from older
// inline comment inside of javascript, javascript takes this as a comment
/* Multiline comment
* Second line.
* ARE HTML names case-sensitive?
*/

function fChanged(form) {
var lngSelected = -1;
lngSelected = parseInt(form.cbxSelect.selectedIndex);
// IE errors out when you use the following:
/*NOTE:
* The next commented line...
* FAILS LOUDLY in IE,
* FAILS silently in FireFox 0.90
* This demonstrates the variable name IS case-sensitive in at least
* two browsers. If there is a browser that it works in, who cares? LOL
*/
// document.txtNEWVALUE.value = document.cbxSelect.options[lngSelected].text;

// The next line SUCCEEDS in both IE and FireFox 0.90
document.TEST.txtNewValue.value = form.cbxSelect.options[lngSelected].text; //<- OKAY in IE and FireFox 0.90

// The next tests have different results based upon the browser being viewed through.
// TEST.txtNewValue.value = form.cbxSelect.options[lngSelected].text; //<- OKAY in IE, NO: FF101, FF090
// TEST.txtNewValue.value = form.cbxSelect.options[lngSelected].value; //<- NO in IE, NO: FF090
// TEST.txtNewValue.value = form.cbxSelect.options[lngSelected].text; //<- OKAY in IE, NOT: FireFox 0.90
// TEST.txtNewValue.value = TEST.cbxSelect.value; //<- NO
// TEST.txtNewValue.value = lngSelected; //<- okay in IE, NO in FF101
return;
}
--></script>
</head>

<body>
<table width="600" border="0" cellspacing="0" cellpadding="0">
<tbody><tr><td width="600"><h1>JavaScript Case-Sensitivity Test</h1>
<form name="TEST">
<select name="cbxSelect" tabindex="0" onchange="fChanged(this.form);">
<option selected="selected">One</option>
<option>Two</option>
</select>
<input type="text" name="txtTest" size="20" tabindex="1" /><br />
<input type="text" name="txtNewValue" size="20" tabindex="2" disabled="disabled" />
</form></td></tr></tbody></table>
</body>
</html>

--
Jim Carlock
Post replies to newsgroup.

:
Thanks Jim, This will take a while to digest and implement. I do appreciate
your time and help.

The following code should update textboxes on all browsers that
support javascript. I've run into problems in the past trying to
get collections of objects to work...


<head>
<script type="text/javascript"><!-- //Hide from older browsers
var lngSelectedGood = -1;
var lngUnitPrice = 0;
var lngQty = 0;
var lngTotal = 0;
function fClearForm(form) {
form.txtUnitPrice.value = "";
form.txtQty.value = "";
form.txtTotalPrice.value = "";
return;
}
function fGoodSelected(form) {
var strTemp = "Blah!";
//var coll = document.all.tags("SELECT"); //PROBLEM SOME BROWSERS
fClearForm(form);
//strTemp = coll(0).options[lngSelectedGood].text; // this works but not used anymore
lngSelectedGood = parseInt(form.cmbSelectedGood.selectedIndex);
//we are opting to to identify by using document.FORMNAME.objectname
strTemp = document.Calculator.cmbSelectedGood.options[lngSelectedGood].text;
// if you had a text box to display what was selected...
form.txtSelectedGood.value = strTemp;
fCalculate(form);
}
function fCalculate(form) {
// someone types in a number
lngUnitPrice = parseInt(form.txtUnitPrice.value);
lngQty = parseInt(form.txtQty.value);
lngTotal = lngUnitPrice * lngQty;
return(lngTotal);
}
function fUpdateSCTFields(form) {
//an array holds info loaded up from a database
form.txtUnitPrice.value = parseInt(Goods[lngSelectedGood][0]);
form.txtShippingCost.value = parseInt(Goods[lngSelectedGood][1]);
return;
}
--></script>
</head>
<body>
<form name="Calculator">
<!-- The nice thing about combo boxes/list boxes denoted by
The first item in the collection of <select> objects is this one...
-->
<select name="cmbSelectedGood" tabindex="0" onchange="fGoodSelected(this.form)">
<option selected>Good #1</option>
.... more options / asp script to load up from db...
</select>
<input type="text" name="txtQty" size="5" value="0"
tabindex="1" MAXLENGTH="3"
onchange="fQtyChanged(this.form)" /><br />
<input type="text" name="txtUnitPrice" size="10" tabindex="12" disabled />
</form>

If you watch the flow of the code, I have one calculate function,
and the onchange="" items inside the combo boxes (or
listboxes) call functions to update disabled txtboxes <input> and
in the end call the fCalculate(form) function to calculate. I
shortened most of this code, but passing the form into the
functions works very well, function0001(this.form).

Also refering to document.FormName.objectName is a great
easy way to reference the objects. But you'll need to tag each
object with a name... (name="txtPrice"). The document is the
global tag in JavaScript used to reference the whole HTML
document. There is a form declaration (NOTE: the name is
case sensitive in all browsers when referencing it in JavaScript).
The Form Name is very important for all javascript code.

I've ran into some problems with javascript collections in the
past not working on NetScape browsers. That was a couple
years ago.

Hope that helps.

--
Jim Carlock
Post replies to newsgroup.

Again, thank you both for working on my problem.

I think i may not have explained it correctly. The problem is not in
passing the 1st and second forms data to the third form on the next page, but
rather what happens when the data gets to the peregform.asp page.

The page pe.asp has two forms, Form1 & Form2, which collect the district
number and club name and pass it on to the third page peregform.asp. Since i
don't have access to a Mac browser I have to guess at this, but I think that
part works fine, since it is server-side scripting. At least it works in all
cases where the Browser security is not set to "High".

The problems on the peregform.asp page are these:

1. when someone chooses one of the first set of options, the correct amount
for that option does not appear in the window. It should be either $250.00,
or $240.00, or $190.00, depending on whether you pick the 1st, 2nd, or 3rd
option. Additionally, if the 1st option is not chosen, then all of the
fields in the President-Elects section should be disabled, but that is not
being done on Mac browsers.

The same is true of the second set of options. The amount does not show in
the window here either. It should be $0.00 if the spouse is not registering,
or is registering seperately, and it should be $190.0 if the spouse is being
registered.

If the spouse is not being registered, the fields that collect his or her
name and club information are supposed to be disabled. Again this is not
being done on the MAcs.

The club and district number do not appear in the database on the Macs either.

Finally the Total registration which is derived from option 1 & 2 is not
being calculated at all.

In some netscape browsers the district and club appear correctly on the
form, but do not get posted to the database.

Would you please fill out the forms and submit them usine IE. and then do
the same thing with OSX and submit it.

You can then look at the results at:
http://www.rotary5830.org/Registrations/Bill/Reports/AllByDate.asp

Thanks again,