The Bridge Posted November 21, 2001 Share Posted November 21, 2001 Greetings all, After a few years of creating single-user standalone solutions and a couple of FileMaker-driven web sites I'm being asked to create multi-user network solutions for a couple of clients. I've adopted the standard of creating "opener" files to bypass FileMaker's Open... dialog, but I'm not really sure if I'm really taking the right approach. I'd love to hear from some more experienced developers out there. What my question boils down to is this: should the opener file do nothing but open databases hosted elsewhere on the network and then disappear, or is it good practice to include other functionality as well? So far, my opener files act as Main Menus for my solutions with a minimum of 2 layouts: the About This Solution layout and a layout containing buttons that open the databases proper. In one case, my Main Menu also has buttons that call specific scripts within other databases, such as for finding and creating new records. This was at the request of the client, who wanted a "one-click-away" type solution. Of course, this approach demands that a copy of the Main Menu be installed onto every computer that will access the databases. I found a great Applescript here on FMForums that seems to offer a fool-proof way of opening the databases using the GetURL function and fields that store the server's IP address (so far I'm only developing multi-user solutions for Mac networks, thankfully) Anyway, am I asking for trouble here, or is my Main Menu approach standard? Many thanks! Link to comment Share on other sites More sharing options...
This topic is 7801 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
Already have an account? Sign in here.Sign In Now