Bruce:
Web pages using popup forms can still be problematic in specific environments, mine being IE8 and MSSQL2008.
I am currently running into three problems:
1. When setting the action for after a Webform’s data is saved to: Insert Another, if the form is in popup mode then it always returns to the WebBrowse procedure, this seems to be true for all the browsers I tried, IE8, FF, and Opera. This may be a case of the documentation needs to be changed (feature does not work in popup mode) and not a bug, if so I can live with that.
2. I have a lookup issue when using a popup form and the lookup field is set to: Force user to use lookup, the field is essentially read-only and the user has to click on the lookup button to select a valid value from a table. In IE8 if I backspace within the field it blows out the browser giving an immediate page has expired message, in FF it is ok as the backspace doesn’t seem to do anything in the field.
You can see the effect here if you like:
http://faculty.cbu.ca/pmacdonald/NT5/NTLookup(Username and password are both: public)
3. Again using IE8 and accessing a SQL2008 backend (TPS seems to be fine) and the form is in popup mode, after opening and canceling the form a few times (not always consistent sometimes twice and sometimes 4 or 5 tries before it happens) the browse will “forget” how many records are available and start to remove navigation buttons and eventually report that there are no records to be displayed. The effect is seems more pronounced in Opera (v11.10) in that it happens on the very first open and cancel sequence. FF does not seem to have a problem with it at all.
You can see the effect here if you like:
http://faculty.cbu.ca/pmacdonald/NT5/IE8_SQL(Username and password are both: public)
It is these numerous combination of browsers and database backends that make developing for the web such a challenge, hats off to you for your patience!
Regards
Parker