Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rothko

  • Rank
  1. Hello there, after having run FM Server 7 for many years on an old, dedicated G5, we're now looking at getting the latest version for our office. The usage is light, normally it's only one or two users accessing one database, with up to 5 maximum. The office is Mac-only, 15 machines accessing files on a Mac Mini Server (mid-2011 model), running Lion Server 10.7.5. It's bad enough making sure that server runs smoothly, so I'm hesitant to use it for FMS. Especially after learning that FMS still relies on Java. I'd rather not have that on a server for security and stability reaso
  2. Sorry. Well, on OS X the easiest way is to create a recurring event in iCal, and as 'alarm' choose 'Open File'. I found it's best to make the script a standalone application first; I did that with Platypus, a third-party app that lets you do just that with any kind of scripts. Platypus gives you all kinds of options, like to automatically quit afterwards, or to run on the background. Surely there are other ways to call the script, e.g. cron if it's a Linux server. On newer versions of OS X, cron has been replaced by launchd, which I found too difficult to handle. By the way, ever
  3. You mean I should give that baby a name? Difficult! It's not much of an application, really.
  4. I thought I might as well share this, as it's taken me a while to figure this out. We needed a script to automatically connect to our FM host's FTP server, and download that day's backup. This shell script here does that, plus compresses and renames the resulting .tar file to date. This will run on any Unix system; we use it on a computer in our office running Mac OS X. #!/bin/sh ############################################################################## # script that downloads a file, compresses and renames it to date # copy to plain text editor and save as fmbackup
  5. Seems like a simple and often-used function, but I need a calculation to restrict field entries to the most basic roman alphabetical characters. Maybe I got a bit rusty on my functions, but I can't think of any function that this could be done with. Nor can I find anything here and elsewhere. Any tips much appreciated!
  6. Well, i do want it to be re-occurring, as part of an automatic synch routine between the two databases. I've now managed to do it. I've created a special layout on which the 'copy all records' script step is run. This layout includes fields that have things like INSERT INTO sql_table (first, last, email, newsletter) VALUES (' and ', ' and '); auto-entered in them. The result of the 'copy all records' script step is then stripped of all its tabs, to create a perfectly formed SQL query. This results in one long enormous SQL query, which is of course longer t
  7. I am working on a way to automatically export all records from Filemaker to an SQL server. I've got this working first via ESS (Via a looping script: go to local layout, set variable, go to SQL layout, make new record, set field, ...). This takes about a second per record. Then I've tried it via the 'execute SQL' script step ("INSERT INTO " ...). This takes even longer. I'm wondering if I can use Multirow-Inserts (see http://en.wikipedia.org/wiki/Insert_(SQL)#Multirow_inserts ) to insert all records at once. Maybe not going back and forth between tables and layouts
  8. Calculated SQL: "insert into contact_test(last_name) values ('" & Substitute(Untitled::name; ["'"; "'"]; ) & "')" note quite right... that last semicolon shouldn't be there. it needs to look like this: "insert into contact_test(last_name) values ('" & Substitute(Untitled::name; ["'"; "'"] ) & "')"
  9. after some further IRC'ing with a very helpful fmsocko I'm going to try to run the script as above, but from a client machine, using ESS. I won't have to buy FMS Advanced, and only one license for the ODBC driver.
  10. I want this script to run on FM Server. Apparently ESS doesn't work there, so here's a way to run it via Import ODBC source. 1. All local FM records have a "last-modified"-timestamp 2. Import from ODBC source. A WHERE-statement checks if there are any records on the SQL side with the timestamp field empty, and imports them. (The timestamp is assigned by FM. If an SQL record has the timestamp field empty, it means it is new and doesn't exist yet in FM.) 3. The next step is to delete all records on the SQL side after downloading the latest additions. Reason: If a record is d
  11. Thanks for your input. After much fussing and confusion it looks like this now. This synching routine should run on just one machine: 1. Set up an ESS connection, with remote SQL table showing up in relationships graph. 2. All local FM records have a "last-modified"-timestamp 3. Import script checks if there are any records on the SQL side with the timestamp field empty, and imports them. (The timestamp is assigned by FM. If an SQL record has the timestamp field empty, it means it is new and doesn't exist yet in FM.) 4. The next step is to delete all records on the SQL side
  12. No, records aren't modified on the SQL side, so I can just import with the ID as matching field. Hang on - should I import or pull using SQL statements? That's not something I'm familiar with at all. Isn't that easier? This way I don't have to check which records are already present on the SQL db.
  13. Hmm I think I may have to reconsider. We can't afford the server version of the Actual Technologies driver plus FMS Advanced; also I keep reading warnings not to use FM as a front-end to SQL databases. So it might have to be an import-export routine after all. At least I wouldn't have to worry about speed issues, having the FM database hosted externally, etc. The SQL database has records added to it, but once entered these never change. So a synchronizing routine could look like this (correct me if I'm wrong) 1. Import from ODBC source, update matching records, add remaining as
  14. We have an office-based FileMaker contacts database which includes some sales management, as well as printing functionality etc. (Typical case for Filemaker.) The client also has a new website, where people can sign up to an email newsletter. This is based on an SQL database. I need to somehow connect the two, so that the client can enter some contacts locally into the FMP database, to receive the newsletter. Likewise, people having signed up on the website should be manageable via FMP. How best to do this? I'd prefer not to get involved with synching-routines if I can a
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.