Jurinicia

Thank you for the answer Stanley. The idea is a very good one, but not the answer for my question. For me it is important to understand, what happens and why the script produces an error in database access. The script does not do any special or irregular, it works like it is documented for AppleScript. May be anyone has an explenation for the behaviour? Thank you

I'm having a problem at a customer. He uses a professional FileMaker database with a FileMaker Server and FileMaker Client 5.5, both on Mac OS X 10.3. I (poorly) don't know, what's happening in this database. When the user opens the database with the Hosts-Menu, everything works well. I wanted to make it easier for the customer to open the database with an AppleScript, so that he does not have to use the way with Open-Menu, click Hosts and than look in the list of databases for the correct one. This script looks like this: tell application "FileMaker Pro" open database "userdatabase.fp5" end tell But what happens if I use this one, is that I get an access problem in one of the databases (userdatabase.fp5 is not only one database, but is the menu-database). I get an error, that I cannot modify the database because I do have only read access or the database is protected. I tested it on several machines with different FileMaker-versions: It happens definitely with using the script. Has anyone an idea what's happening here? Thanks