So far I have kept my entire solution within a single file.
For a while I have been wanting to break it up, but managing users was something I didn't to deal with.
But now I have no choice.
I have a client that has an existing FM system they want me to integrate into mine.
So what did was:
Link the two files.
Write a series of scripts that will create a matching user in the other file.
User are setup with 12345 as default password which they are required to change.
Now when user login they get prompted twice, which confuses them, and then if they fail to set the same password for both logins they get prompted twice every time they log in.
No I know that...
- I can use OD or AD to manage access. But it is not for me to require a client add this service.
- I can have FileMaker set the instead of the user. But that is something user are accustom to being able to do.
So if anyone has thought about this I would love to hear them.
This is not so much fun!
The solution is to have a relationship in each of the files so if one opens it opens the other hidden if it is not already open. To achieve this you have to have a field on the layout to trigger the relational link. The problem here is you have now by passed your on open script for the other file! If you don't have one that is not so much of a problem. If you do you need to work out a way to run it that does not interfere with life too much! Personally I just run them both on open but you need to make sure that isn't an issue. Earlier versions of Filemaker this as much more of a problem than now, these days OnFirstWindowOpen is defiantly your friend here.