Logic for client / server part
I'm now willing to re-write my basic filemaker database into something bigger. My next goal is to make my database multi-user and I saw, that some of my colleagues who uses ACCESS instead, split their projects into two parts: client (interface) + server (database). Main purpose - to be able upgrading/fixing/adding new features for client part, without interrupting users from their job. I'll modify server myself and then just send my user client's part as an update.
Does it make any sense? Do we have good samples of such projects around or nice manual?
Any ideas are highly appreciated!