Filemaker 11 在另一个文件中执行脚本
我想从另一个文件 (B) 运行一个文件 (A) 中的脚本。在文件 BI 中有一个脚本步骤：执行脚本 [“email test” from file:”A”]
文件 A 受密码保护，因此当脚本运行时会出现登录对话框，但我希望它在后台自动运行无需输入密码。文件B是定时文件？我该怎么做？
I want to run a script in one file (A) from another file (B). In file B I have a script step: Perform Script [“email test” from file:”A”]
File A is password protected, so when the script runs a login dialog box comes up, but I want this to run automatically in the background without having to enter a password. File B is a timed file? How do I do this?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在文件A中添加与文件B相同的用户名和密码。
然后在文件A中转到文件->;文件选项并勾选使用登录并填写凭据。
文件 A 将在不要求用户名/密码的情况下打开，当它打开文件 B 来调用脚本时，它将传递身份验证详细信息。
Add the same username and password in File A as File B.
Then in File A goto File -> File Options and tick Log in using and fill in the credentials.
File A will open without asking for a username/password and when it opens File B to call the script it will pass on the authentication details.
我可以立即想到三种技术来运行文件 A 中的脚本，而无需每次都输入密码。
首先，在 Mac 上，登录文件 A 时有“记住我的密码”选项。如果选中此选项，FileMaker 将在文件 B 执行文件 A 中的脚本时查找密码并自动登录。我不知道不知道 Windows 中是否存在这样的功能，但也许可以做同样的事情。
其次，用户通过 FileMaker 身份验证后，FileMaker 将尝试对第一个数据库尝试打开的任何其他数据库使用相同的身份验证凭据。因此，正如 Adam 建议的那样，您可以将文件 A 中使用的相同用户名和密码添加到文件 B 的安全部分。从那里您可以将文件选项更改为使用您传输的用户名和密码自动登录。您现在应该自动登录到文件 B 和文件 A。
第三，您可以手动登录到文件 A 并使其保持打开状态。此技术不如前两种技术强大，因为每次文件关闭或连接丢失时您都需要手动重新登录。
关于安全文件 A 的一些话
可能有密码是有原因的。在执行此类技术时，最好考虑安全性以及如果人们有权访问您的计算机，则应允许他们访问哪些内容。至少，您的计算机在登录时和每当屏幕保护程序停用时都可能需要密码，以确保未经授权的人无法在不应该访问的情况下访问文件 A。
请记住，通过第二种技术，任何获得文件 B 访问权限的人现在都可以使用您的凭据访问文件 A，因此您一定要小心文件共享并让其他人使用您的计算机。
Offhand I can think of three techniques you can use to run the script in File A without needing to enter the password each time.
First, on the Mac there is the option to "Remember my password" when you log into File A. If you check this, FileMaker will look up the password when File B performs the script in File A and should automatically log in. I don't know if such a feature exists in Windows but it might be possible to do the same thing there.
Second, once a user is authenticated with FileMaker, FileMaker will try to use the same authentication credentials for any other database that the first database tries to open. So, as Adam suggests, you can add the same Username and Password used in File A to the Security section of File B. From there you would change the File Options to auto-login with the Username and Password you transferred. You should now automatically log in to both File B and File A.
Third, you could manually log into File A and just leave it open. This technique isn't as robust as the first two as you would need to manually log in again each time the file shuts down or connectivity is lost.
A Few Words About Security
File A probably has a password for a reason. When doing techniques like this it is certainly best to think about security and what people should be allowed to access if they gain access to your computer. At minimum your computer should probably require a password both at login and whenever the screensaver is deactivated just to ensure that people without authorization aren't able to access File A when they shouldn't.
Remember that, with the second technique, anyone who gains access to File B can now access File A with your credentials so you definitely want to be careful with File Sharing and letting others use your computer.