[FX.php List] Two DB's or One?

[Jonathan Schwartz]

Up until now, all my fx.php solutions have been built around an 
isolated FMP database to serve the web.  When there is a primary db 
back at the client, I use various routines to update and synch the 
two, as needed. Obviously, none of the solutions required live 
up-to-the-second data availability on the web.

I'm wondering how many folks are using the same db for both internal 
and web publishing?  If so, how is it working out?  If not, why not?

A little bit more detail...if the client isn't sophisticated, doesn't 
have an IT staff or a fast WAN connection, this would suggest to me 
*not* to keep the web db at the client office.  Rather, keep the web 
db at a reliable web host.

One more detail.  I promise. ;-)....If the solution is in FMP 6, that 
would pretty much rule putting the entire solution in a remote 
hosting location, because FMP is so poor in a WAn environment.

Thoughts?

Jonathan
-- 

Jonathan Schwartz
FileMaker 8 Certified  Developer
Associate Member, FileMaker Solutions Alliance
Schwartz & Company
jonathan at eschwartz.com
http://www.eschwartz.com
http://www.exit445.com
415-381-1852