Thanks. We only use US English, so if I could make it work by setting that language, I woudln't have a problem.
I am becoming somewhat disenchanted with Sharepoint becuase it seems that I have to accept some tradeoffs to make things work.
In my current application, I have a notes list. Each note needs to have a doctor assigned. A separate list contains doctors and I have a lookup column to support linking the doctor. So, when you click to add new note, the OOB sharepoint form is perfect unless you need to add a new doctor that is not in the list. I can put a link to add a new doctor in the form, but cannot update the drop-down column without refreshing the entire form. This means that data saved to the form will be lost.
So, I turned to OOB custom infopath forms and this would allow me to re-query the drop-down data source, but then I loose the ability to spell check my notes.
So, then I turned to qrules and attempted to create a totally new form that acts like the newitem.aspx form; however, the form stops working after about a day. I use a data connection library to make the connection to the form and originally input the location using an externally accessible URL. However, after about a day or so, this URL is converted to an internal URL. Thus, my form becomes unuseable outside of the local site. Any idea why this would occur?