3 locations to bind together.

[lonesomejubilee]

Hi. I am going to be developing three separate databases that basically are identical. They are at three separte locations (possibly a fourth). We are not sure as of right now if we are getting the T1 line to tie them all together. The current plan is to run three separte databases and use a fourth 'master' to pull information from the three individual databases. Of course one would think, why not have one MEGA database and use the network for all 4. Well, first of all I am not sure if we are getting the T1 line, and I don't know much about handling that many people at once. Question (1). What do you think the best course of action is? 3 separte but equals, or one giant network? Question (2). If I stay with the three separate, then do I need FM Server at each separte location (about 5 to 8 users per, but hardly ever 5 to 8 at one time). I heard you can only run 5 at once. There is a lot of data to be entered, but not fast data, an entry every couple of minutes, 24 hours a day. (a chronological logging system). Thanks. Just thought I'd ask the experts before we spend $$

Vandy

[Ender]

I recommend a centralized database with one server if you don't need to do much reporting at the remote sites. Trying to syncronize four servers sounds like a nightmare to me. And then adding features, making minor changes or bug fixes to four identical solutions would be a lot more work.

A T1 connection is great (or a frame network), but DSL works if the solution isn't too big or it's optimized for a slow network.