7 Replies Latest reply on Feb 15, 2016 5:27 PM by Mesial

    Cloned database; dropdowns quit working


      I'm doing analysis of images that involves categorically scoring several aspects of each image.  To do this, I made a database in FMP 13, and made drop-down menus for scoring all the aspects I'm looking at.  I imported data from an Excel file that included the information about each image, including the image filename and path. So for each image, the database displayed the image, the relevant information, and the dropdowns I needed to score it.  It worked great.  Then I needed to score a second dataset.  So I cloned my database, but in the clone my image displays and dropdowns quit working.  (ie, attempts to import new data import any text fields successfully, but imported image paths do not display images, and dropdowns do not function). 


      I tried making a full copy of the database and importing the new data to that full copy. When I do that, then the image paths function, but the dropdowns still do not.  When I check the dropdowns in layout view -- in the cloned or non-cloned copy -- everything appears right and proper. All the relationships are there; the dropdowns just don't do anything when you click on them.  Annoyingly, the drop-downs in the original data from the non-cloned copy still function perfectly fine.


      Any idea what I'm missing here?

        • 1. Re: Cloned database; dropdowns quit working

          please post value list definition for the dropdown.

          • 2. Re: Cloned database; dropdowns quit working

            When you create a clone of the database your global variables lose their values.

            My guess is that you have a relationship that has a global variable in it, and that your value list depends on that relationship or a calculation used in the import process requires it to have a value.


            When you find that global variable add the initialisation of that variable to your on-open script so that it always has the desired value.

            • 3. Re: Cloned database; dropdowns quit working

              If your value lists were based on values in a field instead of static, hand entered values, they are gone when you clone

              • 4. Re: Cloned database; dropdowns quit working

                The dropdowns have custom values.  Easiest way to describe what I'm doing is each image shows (say) forty items, each of which have to be evaluated on two different scales (call them Smith scale and Jones scale, Smith having twenty stages and Jones having five).  So Image One, Item One might be Smith 16, Jones 3.  Image One, Item Two might be Smith 15, Jones 2, and the like.


                I think the problem may not be with the dropdowns value list but with the table to which they refer (call it Smith.Experimental::ItemOne.Smith).  That table has a relationship with the table I import, and the relationship is based on each record's identifying number.  The previous dataset had completely different identifying numbers, so I think I need to create a new table, import data, and remake the new relationship. I'll give that a try and see if it works.



                • 5. Re: Cloned database; dropdowns quit working

                  I checked and as far as I can tell I do not have any global variables.  I think it is a reference problem -- the dropdowns store the information entered in a table, which relates to the imported data by reference number.  But the numbers in that table will all refer to the refence numbers from my first dataset, so the relationship is borked.  Will see if this theory works out.



                  • 6. Re: Cloned database; dropdowns quit working

                    They were hand-entered, but the suggestions here have nudged me in the direction of a relationships problem.  Thanks!

                    • 7. Re: Cloned database; dropdowns quit working

                      Solution: it was a relationships-related problem (the corresponding identification numbers were not in the related table).  I imported the new information to the appropriate tables and the drop-downs work again.


                      I was not able to figure out the problem with the image files, but because they worked when imported into a copy, rather than a clone of the previous database, I made a copy, deleted all records, and imported the new ones.  My database works.  Thanks for the suggestions -- they got me on the right track.