Applescript, FileMaker and Snow Leopard

I upgraded to Snow Leopard over the weekend and, for the most part, everything went smoothly. However, an AppleScript that ran perfectly fine the day before no longer works. Here are the particulars:

OS 10.6.2 FMPA 8.5v2 Dialectic 1.5

This script is triggered by an incoming phone call through Dialectic which finds the callers records in a FMP db.

on handle_incoming_call_action(contact_name, contact_number, phone_or_modem_name)

tell application “FileMaker Pro Advanced” activate try

go to database “Call Log” go to layout “Data Entry” go to current record — (this forces FMP into Browse mode)

set cell “g_Dialectic_Number” of current record to contact_number set cell “g_Dialectic_Name” of current record to contact_name

go to database “Invoices” do script “Dialectic Caller ID Lookup”

Share and Enjoy:
  • Print
  • email
  • PDF
  • Digg
  • Facebook
  • LinkedIn
  • Twitter
  • Live
  • Yahoo! Bookmarks
  • Google Bookmarks

Related posts:

  1. Rosetta & Snow Leopard (WAS: Applescript compatibility under Snow Leopard)
  2. snow Leopard and applescript
  3. Snow Leopard and (old) AppleScript applications
  4. Applescript compatibility under Snow Leopard
  5. Snow Leopard AppleScript Release Notes
  6. spurious timeout on nth Apple event on Snow Leopard (was AS Timed Out Bug on Snow Leopard)
  7. Filemaker Pro and Applescript
  8. Triggering a FileMaker Script with AppleScript
  9. Triggering a FileMaker Script with AppleScript
  10. Triggering a FileMaker Script with AppleScript

Tags: , , ,

This entry was posted on Monday, February 8th, 2010 at 10:41 pm and is filed under Apple. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

  1. Bruce Robertson says:
    February 9, 2010 at 1:05 am

    On Feb 8, 2010, at 11:39 AM, sono-io@fannullone.us wrote:

  2. Anonymous says:
    February 9, 2010 at 3:59 am

    Thanks for the reply, Bruce. I was having a hard time believing that things were broken as badly as they seemed, and it turns out that they’re not. Apparently my Call Log db was corrupted somehow. =: Once I saved it as a clone, the AppleScript worked as it had before.

    I updated it with your suggestions, though. I especially liked this one:

  1. There are no trackbacks for this post yet.

Leave a Reply