Jump to content
Server Maintenance This Week. ×

Using Separation Model with Server


This topic is 4972 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hello folks. Another hiatus from me, but I'm back with another one of my "Where did he come up with THAT one" Questions.

I have a solution that I set up to use the Separation Model back a few years now, mostly to facilitate interface updates. That has generally worked out fine for my single user clients, but one of my clients has asked whether they can install their copy on a server and run concurrent sessions--and I frankly don't know. So, here I am with a few specific questions:

1) With a SM solution, does only the back end database go on the server?

2) If the front end is on each client, are there special steps to link the front to the back?

3) Of course, I assume that Server will handle record locking and data integrity issues with concurrent sessions logged in to the same database. Is that a fair assumption--or do I have to make any special alterations for a networked environment?

I appreciate any guidance that folks can give me!

David

Link to comment
Share on other sites

It is possible to distribute the "interface" file to the mutliple client machines. You would need to add the network path back the "data" file.

But that's kind of only needed in a special (poor) environment (usually heavy graphics, very slow network, etc.). Usually one just hosts the "interface" file on the Server alongside the "data" file, both accessed via relative "file references" ( file:file name ), ie., both files in the Server's database folder. Server takes care of the client sessions and data integrity (maybe the client application does some of this also).

Link to comment
Share on other sites

On point 3...

Yes the server will apply record locking however if you have used scripts then you will need to amend accordingly when there is a record locked and it cannot be updated, for example.

Link to comment
Share on other sites

  • 1 month later...

It would be nice to be able to create a standalone separated model solution that would connect to an existing served database as a thin-client so preferred users could access a filemaker server without having to actually own it - sort of like a portable database interface, but I understand that standalone solutions are not networkable, is that correct?

Link to comment
Share on other sites

The run-time engine is not networkable. Is that what you mean by "stand-alone"?

Everything you ask for can be done right now. Or are you just complaining that you need to buy a license of FMP client to make it happen and it's not free?

Link to comment
Share on other sites

This topic is 4972 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.