Jump to content
Server Maintenance This Week. ×

Question ?


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

Recommended Posts

Scenario: FM Server 5, 6 or so users logged on. One user starts a script to print a report which finds a subset of records in a child file for that report. A half second later another user starts the same script to print a different subset of records. Question: is the second find going to interrupt the first and if so how do you prevent it from happening. I suppose what I am asking is does Server 5 provide each user in this scenario with its own found set of records or does something else happen.

Thank you.

Link to comment
Share on other sites

quote:

Originally posted by geod:

Scenario: FM Server 5, 6 or so users logged on. One user starts a script to print a report which finds a subset of records in a child file for that report. A half second later another user starts the same script to print a different subset of records. Question: is the second find going to interrupt the first and if so how do you prevent it from happening. I suppose what I am asking is does Server 5 provide each user in this scenario with its own found set of records or does something else happen.

FMP Server is multi-threaded and supports multiple users. What one user does does not actively affect another user. Each user is effectively operating seperately.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Consultant

Database Resources

mailto:[email protected]

http://www.database-resources.com

=-=-=-=-=-=-=-=-=-=-=-=-=

Link to comment
Share on other sites

This topic is 8446 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.