Jump to content

Steve E.

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Steve E.

  • Rank

Profile Information

  • Gender
    Not Telling
  1. I want to be able to create indexes of words or phrases in documents in container fields. The documents would typically be PDF or Word files, but there could be other formats (excel? RTF?). Ideally, a (1) search on a word or phrase would (2) highlight the word or phrase, (3) parse or otherwise detect and capture that particular page number in the document, and (4) construct an index of this data. I can see (at least conceptually) how to do 1, 2, and 4, but how can I determine page numbers in the document in the container? Ideas, hints, approaches?
  2. Well, that's what's weird. Since I'm doing this with FM solutions separately installed on each computer, the process resulting in the paths to files on that particular computer should either work or not work on both computers. But the FM solution works perfectly on the computer running Snow Leopard and doesn't work on the computer running Mountain Lion. The problem seems to be that file paths on the computer running Mountain Lion don't work! Here's how I've been testing the FM solution and coming up with this prolem. I'll place test files on the two computers in the same relative place
  3. To be clear, I'm running the latest version of Snow Leopard and my partner is running the latest version of Mountain Lion (OS 10.8.4).
  4. Ideal: Check the first message I posted. I edited it so the file (zipped) would be attached to it. It should be there. It shows up as being present when I go to this page in the Forum and downloads as a zip file that opens fine. I stripped down my working solution to just the relevant parts having to do with ending up with a functional file path in a calculation field that displays as a container so the file can be opened from within the database. I then checked it under various scenarios on both my Mac running Snow Leopard and my partner's running Lion. It works perfectly on the Snow Leo
  5. I've now attached a sample file for people to try. Does it also work correctly on other Macs running SN? Does it not work on other Macs running Lion?
  6. I am using Mac OS Snow Leopard and my partner is using OS Mountain Lion 10.8.4. I've attached a document (or other file) indexing FM solution where the user: 1) selects a file 2) an applescript then opens the file 3) the user can then rename the file, creating a new record in an FM database 4) an applescript then renames the file 5) the file path is extracted and placed into an FM text field either (depending on the file path syntax) via a. an applescript that copies it to the clipboard and pastes it into the field, or b. a Get (DesktopPath) script 6) scripts th
  7. Well, I just did something very very stupid. I accidentally made a change in a script triggered (via "File Option") on a file opening, The really stupid change I made causes the opening window to immediately close, thereby closing the whole file. So, now the database closes automatically upon opening! And this was a nearly (>90% done) solution that I don't have a recent backup of. Is there any way to circumvent or disable the particular script or the File Option setting that triggers it on opening? EEK! HELP!
  8. Its not clear to me why you want to use a value list. If the user interface is going to be in a spreadsheet I don't see the point in translating this data into a value list. The attribute of a value list that makes it useful is for user interface in FM. The user gets to select from alternatives in a single data field. Two things to keep in mind: 1) value lists can be done so ether only one or more than one values can be selected at a time; 2) value lists can be discrete lists (i.e. yes, no, maybe, sometimes) or derived from records in a table (i.e. the names of all customers in the table: sale
  9. That's unfortunate. This s for a document tracking/indexing solution. Ideally, the user 1. D &Ds a scanned document / file into FM 2. calculation(s)/script(s) determine the file path 3. that information is used in a calculation (container) field from which the document / file can be opened 4. the document / file is opened by the user and key ID information (i.e. name, date) is entered into appropriate fields 5. an AppleScript is used to rename the file using the new ID information 6. the file path and new name are used in a calculation (container) field to either directly
  10. I'd like to be able to get the complete file path to files that have been Dragged & Dropped (not inserted) into container fields. None of the "Get" or "GetAs" functions seem to do this. Is there a function or work around to getting the complete file paths? The basic concept is for the end user to drag & drop files into a container field, with calculations/scripts obtaining the complete path, allowing renaming via AppleScript and other manipulations. Any ideas? If the file is "Inserted" this is trivial, but much more time consuming for the end user since they have to navigate to it.
  11. I just tried both insertion and drag & drop of two different jpgs into FM12 container fields. Drag & Drop test: On jpg was landscape and one portrait. Both jpgs were properly aligned, the landscape as landscape and the portrait as portrait. Source of the files was photos downloaded from a camera into IPhoto, then dragged onto the desktop, and then dragged or inserted into the FM12 container fields. Is the problem consistent? Could you try this with photos from a different device and see if it still occurs? Insertions into the container fields as "Picture" shows the images c
  12. A poster on the FM website told me this: "In order for a double click to to open the file, my limited experiments in FMP 12 suggest that: The container field object cannot be optimized for interactive use. Insert File must be used. "Store a reference" must be specified. The storage options for the container field cannot specify external storage--another factor you may not have investigated yet... This is consistent with my experiences in Filemaker 11, but items 1 and 4 are not available options in version 11 so you have fewer ways to keep the file from opening. It seems more and m
  • Create New...

Important Information

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