• 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: Filemaker and Database events
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Filemaker and Database events


  • Subject: Re: Filemaker and Database events
  • From: has <email@hidden>
  • Date: Fri, 11 Jun 2010 22:58:42 +0100

On 9 Jun 2010, at 21:34, Stockly, Ed wrote:

>> FileMaker is a relational database; Database Events is an object database.
>> There is no commonality between them, and both use proprietary file formats
>
> Thanks, that's some helpful information. Although not what I was hoping to
> hear.
>
>>
>> (not that you'd want more than one process accessing the same database file
>> at the same time anyway).
>
> The processes wouldn't be reading/writing to the data at the same time. In
> fact, if FMP could simply export a subset to database events, that would
> work.  The scripts the user is working with only need to read the data via
> database events. [...]
>>

So FMP is just exporting static data sets for remote consumption. If your clients read data from DE but don't write it, it's probably not essential to use a database client-side at all. If it was me, I would output to XML and use System Events to digest that on the client side. Don't know what built-in capabilities FMP has for XML export, but if you need to generate it externally then newer versions of OS X SE can write as well as read XML files.

XML may not be pretty, but lots of applications speak it, and using it for data interchange in distributed systems makes them easier to test and troubleshoot as you can manually create test XMLs for testing an individual component in isolation and visually review the XML-encoded data that's exchanged between components once they're all hooked up.

For example, I recently redesigned one of our in-house automation systems as a distributed application, with all communication done using XML over HTTP. It's a bit of a chore having to eyeball all that XML when debugging the system, but it's still a lot better than any of the alternatives. Glad I did it that way, and I'm no fan of XML.

That said, it sounds like you already have a working solution using DE files, in which case I'm not clear why you'd want to change it now?

HTH

has
--
Learn AppleScript, 3rd edition, Sanderson & Rosenthal:
http://apress.com/book/view/9781430223610

Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net

 _______________________________________________
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/archives/applescript-users

This email sent to email@hidden

  • Follow-Ups:
    • Re: Filemaker and Database events
      • From: "email@hidden" <email@hidden>
References: 
 >Re: Filemaker and Database events (From: "Stockly, Ed" <email@hidden>)

  • Prev by Date: Re: More XML stuff - reading - changing - and writing the file
  • Next by Date: Re: Filemaker and Database events
  • Previous by thread: Re: Filemaker and Database events
  • Next by thread: Re: Filemaker and Database events
  • Index(es):
    • Date
    • Thread