![]() ![]() However, if you want to see the other approach, it’s used in my FM 11 Line Swallowing Bug demo (more on this bug later).īelow is the Relationships Graph for the Virtual List solution, and it couldn’t be much simpler. ![]() …and originally I was going to do a two-part series, comparing these two methods, but when it came down to it, the Virtual List approach struck me as superior in almost every respect, and its performance is unbeatable. view the resulting found set as a list, and use a looping script to parse each paragraph into its own record in a utility tableĢ. So, we need to temporarily slice a monolithic block of text into separate records, and Bruce Robertson’s Virtual List technique is tailor-made for stunts like this. Obviously FileMaker print jobs can, and frequently do, exceed 10 pages, but that’s because multiple records are involved. ![]() To be clear: the 110 inch (≈ 10 page) limit applies to individual records, not print jobs. You can easily store the text of these works in a FileMaker field - one record per work - but how will you generate printed output? Overcoming this limitation is the topic of today’s article and demo file, long documents in FM 11. With the introduction of FileMaker 7 in 2004, that limit was expanded to approximately one billion characters (2 Gb of data divided by 2 bytes per Unicode character), i.e., more than you or I will typically ever need.īut while the capacity of a text field expanded astronomically, the maximum length of a layout remained unchanged at 110 inches (ten 8.5 x 11 inch pages), leading to a dichotomous situation where FileMaker can store vastly more data in a field than it can easily preview, print or output to PDF.įor example, let’s say you’ve decided to build a data warehouse for public domain literary works. ![]() There was a time, many years ago, when the maximum number of characters you could store in a FileMaker text field was 64,000. Also, in FM 12, the maximum layout length and width have been increased to 444 inches (32,000 pt). Update : Preliminary testing indicates that the “line swallowing bug” alluded to below has been fixed in FileMaker 12. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |