11 Replies Latest reply on Oct 10, 2011 3:52 PM by philmodjunk

    Simple Question (I think)

    HSalls

      Title

      Simple Question (I think)

      Post

      OK, I'm about to launch into a new study of FM Pro V11.  I need to know something that I can't pin down in the documentation.  

      I have an FM Pro solution running on an office PC.  It was written by someone else - long gone and hard to find.   OK.

      I want to make some changes to some of the layouts and reports.  I take a copy of all these (.fp7s) home to work on over a few days.  Meanwhile, the staff has added or modified records.  Now when I come back to the office three days later, how am I going to be able to meld my .fp7 layout and form and query changes made at home to the modified FM Pro DB?  In  FM Pro I am too new to understand how changes in layout are incorporated in without sacrificing the new or modified data records I'm going to encounter.  IOW, my new .fp7 files (with embedded and associated tables) are not going to have the added/modified records that were adjusted while I was away working on it.

      Am I being clear?  How do we cope with this apparent out of synch problem without having to discontinue using FM Pro while the changes are being sought?

      H

       

        • 1. Re: Simple Question (I think)
          AnaxThomas

          As far as i can understand from your question is, you want to sync both the databases so that you can update your office database.

          Please check the following help article that explains this process in detail- Help Article

           

          --

          Anax-

          FileMaker- http://www.filemakerrecovery.net/

          • 2. Re: Simple Question (I think)
            rjlevesque

            Is this solution in FMP format or compiled to a runtime solution?

            While at home are you manipulating data or just the design of the layouts?

            Are you adding any new fields or tables, etc.?

            Is this just a FMP solution or is it hosted on a FMP Server?

            • 3. Re: Simple Question (I think)
              HSalls

              @Anax - I'm not really looking to "sync" both databases.  I think, from what I've seen so far, FM does its data store in a much different way than say, MS Access.  Here's the scenario:  I take the fileset home, mess with the layouts only, I don't change any of the actual data at home.  Menawhile, the staff at work has indeed changed some data.  I bring my revisions back to the office on my trusty thumbdrive. At that point, my .fp7 files have the new layouts but don't have the changed data.  How am I going to apply my layout changes when the .fp7 files (containing conflicting data) don't agree?

              @rjlevesque - Solution is in FMP format only, no run time.  I'm not manipulating data, just layouts, forms, reports.  I may add fields if I need to, I may have to add tables.  This is an FMP solution only, not published.

              I'd really like to learn more about FMP.  But if I can't do some work "offline", I'm stuck.

              H

               

              • 4. Re: Simple Question (I think)
                philmodjunk

                Consider modifying the design into a data separation structure at earliest possible opportunity. With a data separation model, you have one file that has all the layouts, scripts, value lists etc that make up the user interface. A second file contains the actual tables. External data source references in the interface file link to the tables in the data file.

                With this structure, you can deploy updated interface elements simply by swapping out the old interface file for the new without needing to import any data.

                Convert to Seperation Model

                • 5. Re: Simple Question (I think)
                  HSalls

                  Wow.  I would never have been able to figure that out!  Other than that link to the other thread, is this "Seperate Modelling" covered anywhere else in the doc?  I'll need to play with it to get a feel.  If I already have a working solution (database app in FM), does that mean that I have to start from scratch to achieve the desired effect?

                  H

                   

                  • 6. Re: Simple Question (I think)
                    philmodjunk

                    The link gives step by step instructions on how to take a unified file and produce data and interface files. It's not terribly difficult to do.

                    "Data Separation" is a general database design concept not unique to Filemaker Pro databases. If you search this forum or others using that phrase, you should be able to pull up a number of discussions on the subject.

                    • 7. Re: Simple Question (I think)
                      HSalls

                       OK, I'm looking at it closely right now.

                      Thank you and thanks to all else.

                      H

                       

                      • 8. Re: Simple Question (I think)
                        Sorbsbuster

                        If you find the data separation model not to your taste, you can simply create a script that imports all the data from the live file into the new file (clone).

                        • 9. Re: Simple Question (I think)
                          philmodjunk

                          And even with data separation, you will still need the import script for updates that require changes to the data file.

                          • 10. Re: Simple Question (I think)
                            rjlevesque

                            Yes, in the data sep model I have always found it best to make a controler file, data file, and design file...but that's how I like to roll.  ;)

                            (I'm impressed Phil, I thought I was the only one on the boards who prefered a data sep model by design.)

                            • 11. Re: Simple Question (I think)
                              philmodjunk

                              Not necessarily "by design". Since it's easy to split a file, I can develop a single file version and then split it when it reaches the point where more than just me will start using it.