I have 2 filemaker files one is my main db the other a db i open from the main db. The problem i run into is that may secondary db has a startup script that gets ignored by my opening comand in the main db.

Main db -> Click -> Open 2 db file -> ignores startup script.

Any ideas?

Your second database need to have its own Start up script, that will be called in its document preference.

HTH

Lee

It has when i open the second db it works perfect but if I open it through the first db it does not run the startup script!! =(

Thomas

if your 2nd db is opened by a script in the 1st db, then its opening script will run. if it is opened automatically because of a relationship for example, then the opening script will not run.

hope that helps!

cheers,

wendy

It is going through a releationship. Is there a way to make it work with a releationship??

Thanks

no, that's just the way FM works unfortunately. if it needs to reference a db because of a relationship, it will do just that & nothing more.

that's why it's best to put steps in your main db's opening script which explicitly open any other required dbs.

cheers,

wendy

So I should make db open db2 ar startup.

Great thanks a lot!! =)

Thomas

Also, be careful not to have a related field to db2 on the layout which db has showing when it opens.

Hmm why??

Sorry for my questions!!

Thomas

You want to avoid the second DB opening automatically due to a related field being visible (that's Queue's point.) Really, the way to deal with it is to have the startup script in the first DB call the startup script in the second DB anyway - just to be sure.

-Stanley

I tried that but, it seems I don't know how to do that.

I have a script opening the db2 from the portal row. "Go to Related Record [show, "RecordIndex"]"

Thats my script so I should include the startup action here already?? And what startup action can hide the toogle window, or zoom?? Sorry totally confused!! +(

Thank you!!

Rather than have your Main db open db2 why not just call db2's startup script directly in your main db's startup script. Like:

perform Script [external, db2:StartupScript]

This will automatically open db2 when you call it. So you don't have to explicitly do an open command.

Cool that worked!! Thank you all for helping me!!

Thomas