Hi,

I am building an application for my fathers company, he has 4 people wishing to access it (read&write -- via TCP/IP peer-peer) on a non-intensive basis.

My questions: My application consists of 12 database files. Reading the blurb I notice that for FM (non-server) the maximum number of database files shareable is 10. What does this mean in reality? Will the host machnine only share 10 of the 12 files it has open? If so, which 10?

My father is running on a very tight budget (hence why he has his son building an application in spare time!) and cannot stretch to the Server edition ($1000).

Any thoughts or help?

James

Technically this is within the parameters of peer to peer (the number of available sockets). I would not expect very good performance however. Be sure to dedicate a machine as the host.

Old Advance Man

Normal FMP will host 50 files. The number of concurrent users is limited to 10.

I concur with Vaughan. With four users, you shouldn't have any problems as long as you're not loading up the host machine and running all sorts of other applications on it all the time.

You may not have to fully dedicate a machine to be the host, just use the best machine you have that gets the least workout from the user.

Again - the "10" is the number of users, not files.

quote:

---

Originally posted by Vaughan:

Normal FMP will host 50 files. The number of concurrent users is limited to 10.

---

There is no way such a configuration will work. If there are 50 files open, it is unlikely that even one guest can connect to it because of the socket limitation. If there are four guests, they can connect to 10 files, but it will be slow.

Old Advance Man

The formula for figuring out whether a multi-user scenario (without FM Server) will work is:

number of users x number of files x 2 must be less than 247

number of users includes the total of the host plus client machines. So if there are 12 files, 4 clients and 1 host the formula is:

(4+1) x 12 x 2 = 120 which is less than the maximum of 247, so this will work, and it may not be too slow if the users are not using the system intensively.