-----original message-----
>>I'm not familiar with Filemaker, however the approach you would take with most other run-time databases (Microsoft Access etc.), would be to create a single backend database that 'drives' one or more run-time frontend applications. With Access this could be an Access database, SQL Server or MySQL etc. I assume Filemaker also supports communications with other standards-compliant DB platforms. Providing FileMaker can split your application into a backend database (able to be shared) and multiple frontend GUI's, you should be able to achieve a multi-user environment without needing to deploy multiple FM licenses. PS - With respect... I would be concerned about a programmer who does not know how to do this.>>
No, don't be concerned. FMP != Access in this regard.
The run time version of FileMaker Pro, at least in version 7 which I'm familiar with, but likely in 8 as well, does not support multi-user configurations. Period. In general, FMP has been weaker than Access at using other databases for it's back-end, although I hear tell that's gotten better, but I'd be astonished if it changed the character of the runtimes. They were designed, from the get-go, to be simple apps, running on one computer only. You can do much more with the versions that run with FileMaker Pro, and with FileMaker Pro server. But not the runtimes.
Peace,
Michelle
--
Michelle Murrain
http://www.metacentric.org
Blog: http://www.zenofnptech.org
.
