Attached is an image of your file not working with the about box information superimposed to show version of filemaker. OS version is OS X 10.7.5

Irrespective, either the browser string is accessible and/or editable or it is not. That's what I'm after because I've got more complicated issues that will crop up later and I'm trying to figure out whether or not I can use Filemaker to resolve them.

It's easy to set up a text field that the web viewer uses as the source of the URL to use. My Known Bugs List Database has that on the Bug Reports layout. You can download a copy and check out how the URL field is used with a web browser. I pasted your URL into the URL field, clicked on the "web" tab to expose the browser and got the result shown in the attached image.

But I am using FIlemaker 12.04 on Windows 7 so this is a bit different from your set up. As I understand it, FileMaker for windows uses a "web kit" derived from Internet Explorer and FileMaker for Mac uses a similar "kit" derived from Safari. So that difference in Web Kits might explain the difference in results.

The browser string is the string that the client (in this case Filemaker, I think) sends to the server as a statement of identity and capabilities. Something, whether it is a local problem on my computer or something more widespread, is causing this string, which is separate from the URL it is seeking, to have this error problem.

If anybody for whom the bridgeview site works could point their web viewer to the whatismyuseragent url and post it here, that would be very helpful. If this string is editable, editing instructions are what I am after.