• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Crash solved; one last filemaker problem remaining
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Crash solved; one last filemaker problem remaining


  • Subject: Crash solved; one last filemaker problem remaining
  • From: Wim Melis <email@hidden>
  • Date: Mon, 26 Feb 2001 01:08:56 -0000

The problem with the crashing text-crunching scripts is solved: it was
indeed caused by Applescript's Text Item Delimiters. After removing every
trace of ATID's, the script now runs solid as a rock.

There's one last cosmetic problem remaining: I'd like to be able to write
to a filemaker field when the script runs, to give some feedback during
lengthy executions.

This test script below works when run from an external editor: you see
the numbers in the FM field changing to '1', to '2', to '3'.

But if I run it as an internal FM script, it'll execute the entire script
before the screen is refreshed, the visible value in the field just jumps
directly to '3' after 2 seconds.

Does anyone know of a way to force FM to update its displayed data?

tell application "FileMaker Pro"
set cell "memo" of current record of window "test" to "1"
delay 1
set cell "memo" of current record of window "test" to "2"
delay 1
set cell "memo" of current record of window "test" to "3"
end tell

Wim


-----
email (home): email@hidden
email (office): email@hidden
http://www.noorderlicht.com * Noorderlicht photofestival


  • Prev by Date: Re:De-lurk and Pop-up windows question
  • Next by Date: Re: magic integer converter number 62?
  • Previous by thread: Re: OS 9.1 & OSA Menu
  • Next by thread: Quitting File Sharing Extension
  • Index(es):
    • Date
    • Thread