Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

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

Recommended Posts

  • Newbies
Posted

OK, I know this happens to others, but I have not seen a solution for this problem.

We have converted a FM6 solution to FM9 and left the files separate. The files are served via FMS9. We only updated the file references and all scripts and calculations. The solution is running just like it did in FM6. All scripts, navigation, etc. are working as expected.

Here is the problem. In FM6 when USER A changed files from FILE A to FILE B, via the Window Menu, the cursor was removed from the original file (FILE A). This meant that USER A no longer controlled a record in FILE A since it was NOT the foremost (front) file.

Now in FM9, when USER A has their cursor a field in FILE A and USER A switches from FILE A to FILE B, via the Window Menu, their cursor is still in the field in FILE A. This means that when USER B tries to access FILE A, via a script step, USER B gets a dialog that USER A is controlling the file and after several clicks of the OK button USER B eventually completes the script and has access to FILE A.

1. Is there a way to automatically "commit records" or remove the cursor from the field in FILE A when USER A switches to FILE B?

2. Is there a way to know that the "window" is not the foremost window and trigger a "commit record" which would take the cursor out of the field?

Any assistance would be greatly appreciated.

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