Setting Up the System Via a Network

I have been successfully using Ebase 2.12 and, now that the three computers in my office are soon to be networked, I am looking for some information on how to set it up so that the program can be used from any of the three computers. I will not have more than one person on the program at a time, so that is not an issue, but I do need to know whether or not a version of Ebase will need to be loaded on each individual computer and whether I will have to purchase Filemaker in order to allow access to the program from each of the computers...not simultaneously.

»

Caution About Wireless Network Connection??

Just wanted to mention that I feel that a plugged-in ethernet connection to the network in a situation like this seems more reliable. I don't have a LOT of data on this, but I have sometimes seen problems that I was GUESSING resulted from slower, or intermittent connectivity using wireless networking. Actually "plugging in" to the network might be more reliable.

--------------------------------------------------
Larry
ebase Consultant
www.quimdas.com

Setting up EbasePro on a network.

The recommended method to provide best performance and data safety is to host ebasePro on a FileMaker server, and to use FileMakerPro/ebase client on each computer. This works great. To remain legal, you'll need a copy of FileMaker per computer. IF... it's three users and no one will be using ebase at the same time... I would recommend putting it on one computer, and then letting the three users share this computer was needed. It's safer, data wise, and cheaper. They just need to change desks/work areas when on the database.
Tim Leed

You have options

Hmmm... Well I think ebase best practices would tell you that in a setting like this you should have a server with FileMakerPro hosting the ebase files and FMP liscenses for each client machine.

However, if you REALLY are not going to have more than one person using the database at the same time, you might be able to get away with installing ebase the files on one of the client machines, and then having the other two machines access them over the network. You probably do need FMP liscenses for each client, although you could try installing the same FMP at each of the three machines and seeing if it complained. To clairify: ebase files should only be installed on one machine, but Filemaker Files need to be on all three.

Since this ISN'T the reccomended best practices way to do it, it's imperative that you have a good backup system and are backing up your db files Frequently (daily is best), just in case something goes wrong with your setup and the ebase files get damaged.

Others have ideas/reccomendations?

Confirmation/Multiple FileMaker installations

I think the advice already offered by Tim and Calista echoes what I might have also said.

Just a little more about the FileMaker installation situation. I believe that in GENERAL, you'll have no problem installing the same copy of FileMaker on several computers. And a VERY close reading of the FileMaker licensing agreement, leads to MY understanding that FileMaker won't insist that the software is only INSTALLED on one machine - their concern is that it is only USED on one machine at a time. (Kudos to FileMaker... this flexibility is a benefit to owners.) I haven't asked the FileMaker legal department this question... it's just my own interpretation - so accept it or don't according to your own sensibilities.

However, many versions of FileMaker will check whether they are the only copy with that install code during their "startup" process. So if you try to start up the SAME copy of FileMaker on more than one machine, be prepared to get a message indicating that you can't run the same copy TWICE.

The option of having a separate copy of FileMaker installed on each machine used to access the database is really the safest/most reliable. Copies of these V5/5.5 can be had from ebay for about $70 if you're patient. I've acquired several copies for clients in this fashion...

--------------------------------------------------
Larry
ebase Consultant
www.quimdas.com