• 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
re: Slow FileMaker Scripting Code
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

re: Slow FileMaker Scripting Code


  • Subject: re: Slow FileMaker Scripting Code
  • From: David Crowe <email@hidden>
  • Date: Fri, 24 Nov 2006 09:00:00 -0700

Thanks for all the feedback on the slowness of FileMaker filling in a large number of fields on a large number of records.

I'm thinking that my original idea is probably best, creating a layout with the fields in the right order for the "create new record with data..." to work properly. The script can actually validate this layout and refuse to run unless it's correct.

The alternative of writing to a text file (comma or tab separated) is also viable, but it needs more code to manage the file (deleting an old file if it exists, cleaning up afterwards) and you need to do something about fields that contain whatever field delimiter is chosen.


Regarding Malcolm's idea about bundling the FM with the AppleScript, I've already done that. I've developed an application designed for personal management of many meetings, each of which has many documents associated with it. This includes creation of agendas and meeting reports (based on notes taken for each document). It also includes a calendar as a method of accessing the meetings. It still needs more work to replace the FTP component, which was based on a filemaker plugin that was never fully updated to OSX. I'm thinking of using Fetch instead (although curl is a possibility too). FTP is used to synchronize documents between your personal computer and a shared server. Other protocols are certainly conceivable too.


What I was trying to do is to separate out one piece in a way that other people could adapt to their applications fairly easily. Another piece I have (although it's a much tougher job) is a synchronization between Apple's Calendar and a database. It's much more complex because a calendar is not simply a list so more database tables are involved in the synchronization. I don't know if it's ever going to be feasible to separate that out.

My plans are to make this software I'm calling "Meeting Tracker" a freely accessible, open source project (although FileMaker isn't the optimal software for doing open source, I think it's still possible). I've been using it personally as I've been developing it over the past few years and have over 8000 documents associated with over 600 meetings in the database (obviously I spend far too much time in meetings and writing reports). (imho) This is a vastly superior approach to writing an individual Word file for each meeting because it provides really good search capabilities through meeting reports. Plus notes taken can be included in different reports for different purposes etc.

If anyone is interested in checking it out at some point, please let me know. It's certainly not ready for prime time, but maybe alpha testing for brave people with a bit of time on their hands.

- 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: Slow FileMaker Scripting Code
      • From: Malcolm Fitzgerald <email@hidden>
  • Prev by Date: Fwd: loosing finder cut'n paste after bad scripting System Events
  • Next by Date: Re: Slow FileMaker Scripting Code
  • Previous by thread: Re: Slow FileMaker Scripting Code
  • Next by thread: Re: Slow FileMaker Scripting Code
  • Index(es):
    • Date
    • Thread