What is "NULL"? FileMaker has the function IsEmpty(). There is no 'null' in FileMaker.
What if you check the lenght of the source of the webviewer instead of the content?
Again with the CF...
I just want folks here to know that IsEmpty() is a native FM function and using "NULL" (a SQL 'value') may be confusing to some.
The Webviewer does not have a source, the second mark script step on both the above images is;
Set Web Viewer [Object Name: "WebViewer"; URL: $HTMLResults]
So it is updated on the fly, rather than having a source
Just because your wrote the value doesn't mean that it doesn't have a source. Looking at the source will show where the $HTMLResults content is getting cut off (perhaps an invalid character, etc). Comparing the Webviewer object source to the $HTMLResults variable should point you in the right direction.
Source in this sense isn't a URL, it's the source HTML that the webviewer is displaying. Just like viewing source in your traditional browser.
I've already checked this, there is a test in the data viewer for the length of $HTMLResults, this variable has 46.7k characters in it, but after it is written to the WebViewer, it becomes 9.5k characters...
This is where I get confused, that in updating the WebViewer, it is losing 3 quarters of the content.
You already posted that the length is different... that' doesn't help troubleshoot/fix the problem. You need to fetch the content and compare it to the variable - see WHERE they start to differ in the actual text (not their lengths)
Sorry, you mentioned looking at the source, but the source is good.
I've had a look for bad characters, but there aren't any, I use Substitutes to remove anything unwanted before it is then used as a result
1 of 1 people found this helpful
What makes you say your source is good? Wim's suggestion about checking your source length is to help narrow dowm the problem.
$HTMLResults -> WebViewer Source -> WebviewerContent
Your source isn't good if it isn't returning all your data (only 9k).
Compare these three side by side and see where the data gets cut off:
My guess is that there is an invalid/invisible character in the $HTMLResults that is causing the source (and resulting content) to be cut off.
The advice that Wim and PalmDBS have been offering seems really sound to me, despite the tests you've mentioned having already performed.
I think that PalmDBS's last post, suggesting a side by side by side comparison of data (not just length of data) would be a very helpful exercise.
1 of 1 people found this helpful
Bad characters, invalid HTML, yes. Also 'browsers' ignore duplicate white space. " " becomes " " (without the quotes), for example. Pretty-formatted HTML is for humans.
-- sent from myPhone --
I've looked at the three different items as suggested by PalmDBS, The Source is is the same as the Variable that is creating it;
Having looked at this a bit closer, when I take 'Length' out of the source attribute, and try to view the details behind Source, I actually end up with the same cut down detail as what comes out of the Content, the 9k characters, which is extremely strange. From what I understand there is no limitation in the data viewer?
Anyway, I have a point to start looking at as all of the details behind each item all end at the same record and field.
It turns out that this is a double spacing issue, but not in a single record, it is where the user has ended one record with a double space, and some how managed to start the next record with a double space, meaning there in the results, it is get " " x4, and the HTML doesn't seem to like this.
I shall have to see if I can add this as a correction as part of the creation code.
Thank you all for the help, and assistance in getting this sorted.
Something I have done for multiple spaces is to substitute out a run of two spaces like so...
[" " ; " "]
That way, you do not need to substitute every single space with a non-breaking space (the html entity ) so html will still wrap where needed, but show the space where appropriate. That might help here.