This is ridiculous...FM is adding a "/" after the .com in a Open Url calculation. I have tried adding a "" like a previous post recommended and now the calculation is saying that the text string does not end with "" when it in fact does!

I am creating the url using the combination of three fields. NOTHING seems to work.

I have another Open Url calculation that is strictly text and the "" did work, but it is not working on the combination field calc.

Can anyone help, this is completely frustrating!

This is ridiculous...FM is adding a "/" after the .com in a Open Url calculation. I have tried adding a "" like a previous post recommended and now the calculation is saying that the text string does not end with "" when it in fact does!

I am creating the url using the combination of three fields. NOTHING seems to work.

I have another Open Url calculation that is strictly text and the "" did work, but it is not working on the combination field calc.

Can anyone help, this is completely frustrating!

This is ridiculous...FM is adding a "/" after the .com in a Open Url calculation. I have tried adding a "" like a previous post recommended and now the calculation is saying that the text string does not end with "" when it in fact does!

I am creating the url using the combination of three fields. NOTHING seems to work.

I have another Open Url calculation that is strictly text and the "" did work, but it is not working on the combination field calc.

Can anyone help, this is completely frustrating!

Try dropping the http:// and/or www. prefix from your URL, e.g. instead of "http://somesite.com/something" use "somesite.com/something".

It will still add a slash at the end, which may be a problem with some URLs.

Try dropping the http:// and/or www. prefix from your URL, e.g. instead of "http://somesite.com/something" use "somesite.com/something".

It will still add a slash at the end, which may be a problem with some URLs.

Try dropping the http:// and/or www. prefix from your URL, e.g. instead of "http://somesite.com/something" use "somesite.com/something".

It will still add a slash at the end, which may be a problem with some URLs.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

will this work if my url is generated using the values of some fields? for instance, the urls will point to a file defined in the filename field. thanks.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

will this work if my url is generated using the values of some fields? for instance, the urls will point to a file defined in the filename field. thanks.

If you're running Internet Explorer forget about Open URL and try using Send Event with this syntax:

iexplore.exe "http://www.yahoo.com"

This just simply calls up the IE browser and passes the address to it. I've been using it since the bug was first discovered and I haven't had any problems. I don't have to worry about other browsers because we are a Windows shop from wall-to-wall.

will this work if my url is generated using the values of some fields? for instance, the urls will point to a file defined in the filename field. thanks.

Sure, you would make a calculation something like this:

"iexplore.exe http://www.thesite.com/folder1/folder2/" & tableName::FieldName

Sure, you would make a calculation something like this:

"iexplore.exe http://www.thesite.com/folder1/folder2/" & tableName::FieldName

Sure, you would make a calculation something like this:

"iexplore.exe http://www.thesite.com/folder1/folder2/" & tableName::FieldName

Dropping the Protocol prefix and / or the 'www' does not work either. I am having the same problem.. allthough, sometimes it works and other times I get the extra '/' at the end of the domain. Surely this behavior was not intended?

We used to have a similar problem earlier, with the lower-case URLs; now it's a slash. Perhaps the same solution will work. On a Mac you can use Perform AppleScript step with:

set theURL to cell "theURL" of current record

tell application "loginwindow" to open location theURL

Apparently this behaviour is different in 7.0v1 and 7.0v3 - the extra '/' does not appera in v1 , but if you drop the protocol prefix (http://) in v1, the URL will not work. In v3 you get the extra '/' if you leave the protocol prefix, but works fine if you drop it. I suppose that you should either stay with v1 if you have particular protocols to address (although I have not tested with other than HTTP). or update to v3 and drop the protocol prefix.