4 Replies Latest reply on Sep 8, 2016 4:02 AM by beverly

    Server Upgraded to FMS 14 breaks solution... any help appreciated.

    Hi_Fi_Guy

      Team of Americans working on an archaeological site in the Mid-East. We built our solution using FMP12 a few years ago. Our university upgraded to FM Pro, Go, & Server 14. When upgrading server a few key pieces of our excavator's field solution broke. All advice appreciated.

       

      Lot Numbers:

      Our Archaeological lot numbers are generated using a calculation that combines 2 key pieces of data with a serial number, example: AB15B.00128 This has worked for the past 4 seasons without fail. After upgrading to FMS14 the . in the lot number breaks the solution. The Lot number is saved into the DB but is no longer visible to the Lab scientist checking in the lots on their form... the lot numbers are no longer visible on their forms.

       

      Temp workaround. I discovered that switching the . to a - or other punctuation mark would allow the lot numbers to be seen on the Lab form by those in the lab. This is a temp workaround as the - is scientifically incorrect. We need to figure out why it is not working with the . but will work with any other punctuation we tried. FYI: The . works when running a copy of the DB locally but NOT from FM Server.

       

      Excavators:

      Excavator's need to enter their 3 Letter ID on their field lot form to identify themselves as the person in the field logging in that particular lot. In the past we have accomplished this by having them select their ID from a drop-down menu which pulls the list of Excavators from a "Team ID" table. Since upgrading FM Server excavators may have to choose their ID 2 times for it to take effect and even then 25% of our forms are coming back with the excavator field blank. At first I thought it was user error or slow data transfer or something but it seems to be something is actually broken or not working correctly since the server upgrade. I have done test where I see the form accept the excavator's ID and it shows clearly on the form, however if I check the actual cell data in the DB the excavator ID is not there.

       

      I'm maintaining the solution here in the Mid-East and has at my disposal my copy of FM Pro. I helped build the original solution, along with two other developers who I would consider to be far more knowledgable than myself in these matters. Any feedback or help this group could provide would be very much appreciated as I am trying to keep 8 archaeologists working in the field and lab happy and ensure their discoveries are all logged in correctly. I know this post is more of an overview of the problems we are experiencing since the server upgrade. I am happy to answer any questions about the hows and why's of the solution to get to the answer. Everything has worked perfectly until the server upgrade.

       

      One further question about FILTERING LISTS

      When using a pull down menu to view a list of items, like lot numbers, on a form. Is there a way to filter the items by creation date? We are on the 4 season here and I'd like to have the lab scientists only see this season's lot numbers so they do not accidentally choose a lot number from previous seasons.

       

      Thanks again,

        • 1. Re: Server Upgraded to FMS 14 breaks solution... any help appreciated.
          wimdecorte

          some prelim questions:

          - the lot number is defined as a text field in the table?

          - can you actually search on lot numbers with the "." in them and get correct results?

          - (check the format options of the lot number fields on the layout to make sure it is not formatted as some variation of number / currency / ...)

           

          - are the clients still using 12 or also 14?

          - what are they mostly using?  FMP or FMGo?

           

           

          Lot numbers selection: what you need is a conditional value list, one that uses a relationship to filter out only this year's lot numbers.

          • 2. Re: Server Upgraded to FMS 14 breaks solution... any help appreciated.
            Hi_Fi_Guy

            some prelim questions:

            - the lot number is defined as a text field in the table?

            It is a calculation made of Text + Text + Number (Serial Number)

             

            - can you actually search on lot numbers with the "." in them and get correct results?

            In the past yes, now any info after the . is ignored in a search. Example: a search for AB15B.0029 would return ALL records starting with AB15B the ".0029" being ignored.

             

            - (check the format options of the lot number fields on the layout to make sure it is not formatted as some variation of number / currency / ...)

            Only the serial number is formatted as a Number. Testing with the serial number changed to Text yielded identical results.

             

            - are the clients still using 12 or also 14?

            - what are they mostly using?  FMP or FMGo?

            Our team are using iPads running FMGo 14 along with 2 laptops running FMP 14 (myself and the PHD who oversees the project for the university).

             

            Lot numbers selection: what you need is a conditional value list, one that uses a relationship to filter out only this year's lot numbers.

            I was thinking along these lines... Thank you!

            • 3. Re: Server Upgraded to FMS 14 breaks solution... any help appreciated.
              Hi_Fi_Guy

              Follow up on this topic. The problem was multi-faceted.
              - Added UUID's to each table that could create a record
              - Changed the way Periods were implemented in our Lot Numbers. Now part of the calculation instead of static auto-enter data.

              - Used conditional value lists to filter Lot Numbers by date, material type, etc.

              These changes solved all of the problems we were experiencing with with the database.


              Thanks to all who replied.

              • 4. Re: Server Upgraded to FMS 14 breaks solution... any help appreciated.
                beverly

                is this related to this thread?

                and can you also mark this question as answered?

                beverly