Re: Filemaker and Database events
Re: Filemaker and Database events
- Subject: Re: Filemaker and Database events
- From: Geoff Graham <email@hidden>
- Date: Tue, 15 Jun 2010 15:02:32 -0400
I ran into a similar problem a while back (ginormous phone switch log file with a varying number of "fields"; in this case separated by spaces for plain text printed columns). What I did was to import the thing as .txt into a single field, then created a number of calc fields to represent the "columns" I wanted. I was able to use a handful of If and Case statements to account for different data (as in: Case (type = "Sports; MIddle (Txt1; 5; 10); type = "Movie"; ...).
For the millions of lines I was looking at, I was surprised at Filemaker's speed in this case. Since there was no relational data to consider, I didn't bother to make the calcs unstored; I wanted max sorting and exporting speed and got it.
Geoff
On Jun 11, 2010, at 8:51 PM, email@hidden wrote:
> It starts with pipe delimited raw text file with thousands of records each with 15 to 18 fields. (It's a fixed fileformat that is used in a number of applications, that won't change)
>
> Each file lists everything on TV on 90 different channels for one day.
>
> Sometimes we work with one day's listings, sometimes one week's listings and sometimes with three week's of listings.
>
> The file format is fixed and not internally consistent. Movies and sports programs each have a different number of fields than the rest of the programs.
>
> Importing into FM from appleScript is a real pain because you have to convert to XML (which takes a long time) then save the xml file to a standing file that a filemaker script can recognize for import.
>
> Importing the same data into DE takes about 1 minute, as opposed to 10 in FM.
>
> But, if I could import into DE, then read those files in FM, that would be cool. Then I only touch the raw files once, get the speed of DE working with inDesign and the UI goodies.
>
>
>
> ES
>
>
> On Jun 11, 2010, at 3:42pm, Bruce Robertson wrote:
>
>> Well, it can be done, after all Database Events files are simply SQLite. Also, I don't see why an XML process would take any time at all, I'm curious what method you used and how many records are involved. If you're importing data into FileMaker, the source of the data (FileMaker, CSV, XML) may not have much to do with the speed.
>>
>> Bruce Robertson
>>
>> On Jun 11, 2010, at 3:32 PM, email@hidden wrote:
>>
>>>>
>>>> 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?
>>>
>>>
>>> Yes, one part of the system is working and I don't not want to change that.
>>>
>>> I had started by converting my raw data to XML, then importing into filemaker, then calling FM from my script, but that took way too long, both to initiate and at runtime.
>>>
>>> Once the data is stored in DE access is vitally instant, which is needed since it's heavily involved with user interaction. And it's even faster to convert and store the raw data in DE than it is to convert to XML and import into filemaker
>>>
>>> We use the same data for a variety of purposes, and I'd rather not import it into a second database system in order to edit and repurpose. If both systems could read from the same data that would be ideal.
>>>
>>> If not, I'll get by.
>>>
>>> Sure is frustrating using applescript with FM pro. I'm ready to give up on it.
>>
>
> _______________________________________________
> 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
_______________________________________________
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