Runtime as multi user?

[EllenG]

Does anyone have a solution to allow a runtime application as multi-user, without the expense of FM Server? I am able to run the application as "shared" on a network, but it will only allow single-user access. This works fine for 99% of my clients, but I have a few who would like the ability to independently and simultaneously access and update data from multiple networked PCs. I also have a few potential clients that would purchase my software if I can make this work!

My application is developed under FM6 runtime.

As an alternative, is there an easy and inexpensive way to "sync" multiple versions of the software, without having to log every update and script a solution?

Is it possible to run an FM6 application as multi-user in a "shared" folder if it is NOT runtime???

Thanks for any help.

[David Holmberg]

A runtime can't be run as multi-user, don't have any anwers for the rest of your questions.....

[DigitaLab]

I agree with David... However, I would like to ask you how many users your application will host? Maybe you clients needs a VLA from FileMaker.

[EllenG]

My application is not web-based. I am hoping to add that capability in the future. It is distributed as a stand-alone application and runs on PC or MAC platforms. It is a Herd Management system predominantly for alpaca and llama breeders. Most of my clients just run the app on one computer, or may also copy it to a laptop when they travel. A few run it "networked" in a shared folder, so they can access the app from their office or barns, and are OK with the single-user limitation. There are a few clients (and potential clients) that have large herds with several barns and they employ ranch hands. They want to be able to access AlpacaEASE from any of the networked locations simultaneously. And, of course, runtime does not allow it.

Thanks for the replies.

[Rigsby]

The Good, the Bad and the Ugly!

The Good

You need to develop your solution as a

[Søren Dyhr]

Regarding the UGLY - if say the entire network is mac'ed ...wouldn't it be more convenient to have another database acting as server instead of the folder with the vast number of ultra tiny files? I seem to remember that you by double tell statements can make you applescript work on another machines OS adressing issues on that machine ...because filemakers applescript implementation includes "transactions" which allow users in turn to make the application deaf to appleevents it used to respond to, and when the task is completed return to listening mode.

It should probably be made as a handshake operation where the server then recieves a parameter from the caller containing a callerID who locks it up for outside communication ...The server writes back to the caller via the parameter recieved again via double tell's but now is it the servers OS that writes...

Just a thought!

I wouldn't be surprised to learn that this is just as bad a violation as CGI'ing a bound version!!!

BTW isn't the process you dsicripe very close to SyncDek's way, except they use imap mailing instead??

--sd

[maxwellk]

Like Soren mentioned, SyncDek (http://www.worldsync.com) is a viable way to 'sync' data between FileMaker runtime solutions, and we've had a good deal of success with it. Although you don't have to purchase FileMaker Server (and a server) or a FileMaker Pro license for each user, you do need an email account and a SyncDek license for each user.

[EllenG]

Thanks for all the feedback. I've considered some similar options, like creating a "log" file with date/time stamp, file id, record id, field name and data and then exporting those files daily and have an import script to update records from that log file daily. But that's a lot of work and re-programming! I use global update fields and SAVE in many of my screens, but not all (mostly with related records, such as medical, breeding, etc. that are tied to an animal record in the main HERD table.) I also (briefly) looked at SyncDek, but wasn't sure if that would work and also the cost can be as bad as FM server, since it has to be licensed on each PC. Perhaps I'll take a closer look and try a demo, if available.

I think my best option is to web-enable the app. I haven't begun to look at that in depth, so I don't know what's involved and I don't know CDML or Lasso, so I may be limited. It is however, the next step I want to take with my app. My son does web design, so we are looking at getting a server and be able to provide a "turn key" system to breeders: "Cookie-cutter" web-site, web hosting, domain name, email and their AlacaEASE herd database as a complete package. I think I can also develop an automated export/import from the client-side runtime app, so users can still run that on their home PC, then send periodic updates to the web and vice-versa if they update the web side.

Anyone doing something like that, I would be very interested in seeing it and any pitfalls encountered.

Thanks again!