• 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
If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')


  • Subject: If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
  • From: David Crowe <email@hidden>
  • Date: Sun, 22 Oct 2006 22:25:31 -0600

I am actually quite familiar with the FileMaker AppleEvents database but, as Michael Vinca pointed out, it hasn't really changed much over the years (I've been around long enough to notice that). And like AppleScript dictionaries they often don't give you that much information. I got enormous help from this mailing list in the past, without it I'd never have got started writing AppleScript because all the books and online help didn't seem to explain why my scripts all refused to work in the early days.

One of the things that I have found with FileMaker 7/8 (as opposed to versions 6 and lower) is that it is critically important to reference a Layout above just about everything else.

If you think about it, from a Layout FileMaker can determine the table instance and the database, but not the other way round. Virtually all my scripts communicating with FileMaker have had to change because of this.

With the current problem, I have included many combinations of tell database/table/document/layout ... and all of them lead me to the conclusion that "create new record" goes no farther than the document level and creates a new record in whatever layout/table/database is visible to the user.

I've mentioned a really simple two-table FileMaker system that I set up to perform testing, and provided real code that doesn't work how I'd like it to work. My critics have provided suggestions, which I've tried, but not code proving that "create new record" can create a record in a different table/database/layout than is currently visible. If I'm so dumb, it should be easy to write the script that will prove it.

I think I can usually work around this, my applescripts are generally run by the user via a FileMaker button, but I was hoping that someone would be able to give me specific code to identify the correct way to get "create new record" to act on a table/database/layout that is not visible to the user or confirm that this is indeed a bug (or 'limitation' or 'design feature', depending on your perspective).

Regards,
    David Crowe
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/mailman//archives/applescript-users

This email sent to email@hidden
  • Follow-Ups:
    • Re: If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
      • From: "Gary (Lists)" <email@hidden>
    • Re: If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
      • From: Bruce Robertson <email@hidden>
    • Re: If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
      • From: Malcolm Fitzgerald <email@hidden>
  • Prev by Date: Re: How can I open attachment in Mail ?
  • Next by Date: do Shell Script & shell Script
  • Previous by thread: unsubscribe
  • Next by thread: Re: If I can defend myself... (was 'Re: FileMaker (Pro Advanced 8) bug?')
  • Index(es):
    • Date
    • Thread