Jump to content


  • Posts

  • Joined

  • Last visited

Boot's Achievements


Explorer (4/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges



  1. This is so great Tony. Even though it's months after your post, thanks heaps! You've saved me from the asylum. For the sake of posterity and other searchers, this extra blank row problem also applies to HTML exports, and probably other formats too (CSV, XML etc). Cheers, Craig
  2. As a postscript to the initial question for the sake of anyone else trying to implement a web export of pictures in the future, beware of a problem that I have discovered: As of version 8, Filemaker has a very annoying insistence upon resizing the display of images based upon their dpi setting. This means that two images of the same pixel dimensions but differing dpi settings will display at different sizes in Filemaker (like they would in a print layout program, but very unlike anything to do with the web, where dpi is ignored). Worse yet, Filemaker actually calculates its stored height and width data to display the image at the print size. This means that any attempt to export that data into a web page layout will carry over the wrong pixel dimensions, and you'll get typically squashed or tiny pictures displaying for all those that happen to not be at the standard 72 dpi used for screen viewing. So you can either leave out the dimensions from your html code, which gives slower page loading, or fix it in another program afterwards. Dreamweaver, for example, has a resize button that will do the job one image at a time, and somebody offers an extension that will do all images at once (search the Dreamweaver exchange). Better yet, submit a request for Filemaker 9 and beyond to offer optional handling of image display to suit both print and web workflows.
  3. Wow, fantastic. Thanks heaps for this -- it's going to save me hours of laborious work. I can't believe it's so easy. I'm working on implementing it now, and it looks good so far. For the sake of anyone else reading in future, I've had to create a global field containing a double quote to get the formulas to work correctly with all the quotes required for html. So, one of my calc lines looks like this: "
  4. No responses so far, so maybe Filemaker is unable to concatenate data from several records into the one place. I'm surprised. Maybe I can do it by sending a system event to a Windows command-line utility that will concatenate or splice text from a looping Filemaker script into a text file. It's got to be possible.
  5. I notice a problem with images that have been added en masse through Filemaker's import folder function. A GetAsText ( Image ) string for one of these records returns only the following minimal information: image:/D:/Database/Subfolder/apricot.jpg As I'm trying to extract the pixel dimensions that are usually present through a manually-added image, I'm at a loss as to how to entice Filemaker to get the full information, like: size:501,341 image:My Images/picture.jpg imagewin:/D:/Database/My Images/picture.jpg Any body have any idea why these images are treated as second-rate?
  6. Wow, that's so clever Daniele - your solution actually seems to work. Amazing. I've run into another problem with images imported automatically, however, and have posted it as a separate topic (they seem to be treated differently and the pixel dimensions aren't present). Thanks heaps.
  7. Is there any way to isolate the pixel dimensions from a GetAsText ( Image ) string so that they can be used to plug into html code? GetAsText ( Image ) produces something like: size:501,341 image:My Images/picture.jpg imagewin:/D:/Database/My Images/picture.jpg ...whereas html requires syntax like: height="341" width="501" ...so if I could isolate the height and width dimensions into individual calculation fields, I might be able to plug them into another calculation that generates the body of a simple web page for all the images of a given set (see my previous question). I might have a hope of solving this myself, but am stumped by the variableness of the pixel dimensions. They could be anything from 2 digits each to four digits each, and all combinations in between (e.g: size:97,286 or size:1024,768 etc). Is this solvable?
  8. I am hoping to take a found set of images in container fields and generate the guts of a simple web page in a calculation field using repeating segments of code like the one below. I already have the filename isolated in a calculation field, and have posted another question in this forum about isolating the pixel dimensions too (though dimensions are not essential). The repeating code segment looks like this: filename Contents of a description text field The above should be relatively simple to generate with a calculation, but the difficulty for me is how to get it to loop through a found set and add each repetition into the one text field or text file so I can copy and paste it into an html template file. In other words, how to wind up with the following all in the one place: pineapple.jpg A pineapple growing in a Fiji plantation guava.jpg Guava fruit, rich in vitamin C ....etc.... Any help hugely appreciated.
  9. Thanks Kent - I'm looking into the Troi File plugin right now and it certainly does look intriguing.
  10. Despite my best attempts at avoiding this scenario, I now need to move lots of images en masse into different folders before they start breeding with each other, etc. The problem is that they are all referenced in container fields, and when I move them Filemaker loses track of where they've gone (even though it might only be to an adjacent folder). So, is there any way I can do a search and replace type of operation on the referenced paths that Filemaker stores for each image or is this information hidden within the binary bowels of the program where I can't change it? In other words, it's as though I need to invoke a GetAsText string for the container and somehow edit it and have this info replace the actual file reference. Any help in avoiding the manual re-linking of hundreds of images would be appreciated.
  11. Is there a simple way to have one field automatically updated whenever another field has data added to it? I have two fields, a text field and a number field side by side. The second one is often blank, but whenever it has data added it means that the first field needs to be changed too: Field one has a text value list such as "Cancelled", "Waiting", "Possible", and "Submission Number". Field two is a number field whose sole purpose is to describe which "Submission Number" is being referred to, so that whenever it has a "1" or "2" or "1b" in it, the first field should always be changed to "Submission Number". I've tried to make this happen automatically through validation options, but they don't seem to work for me.
  12. Aha! That should do the job. Silly me for not finding this one. Thanks heaps.
  13. Filemaker seems to display linked images in container fields according to their print size (ala QuarkXpress) rather than pixel dimensions (ala photoshop & web browsers). This makes some low-resolution thumbnails unviewably small in filemaker if they have been generated without adjusting the dpi setting -- a common mistake that browsers mask. Is there a way to change filemaker's behaviour so that the dpi setting is ignored for screen display purposes?
  14. I'm working on a script to export images and rename them but I've noticed a really weird thing with the Export and Send Event steps. No matter what I specify as destinations or locations, FMP subverts it by somehow sending the location of the last folder I from which I imported an image. In other words, I import several images from an "imports" folder, then try to export and rename them in an "exports" folder, but my scripts either don't work or do work but send everything to the imports folder. I've tried it with command lines and batch files, always with the same result. The only cure I've found is to artificially import a file from the exports folder first to set that as the most recent folder location. Unfortunately, this workaround doesn't do the trick when scripted, only when performed manually through an Insert Picture (or File) navigation box. What on earth is going on? Is there a script step to flush these ghosts out of the machine?
  15. Søren Dyhr has solved this problem beautifully in another post within this same sub-forum. Look for my post entitled: "Is it really impossible to extract filenames?" You just set up the name field as a text field with an auto-enter calculation, and apply Søren's formula.
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.