Forum Discussion

Daniel Colardelle's avatar
Daniel Colardelle
Copper Contributor
Aug 30, 2016

Excel 2016 french L1C1 reference style issue

Excel fr, Windows 10 fr (1511)

When used as a string, you could write :

=INDIRECT("L1C1";FAUX) (returns A1 value).

Now, since a few days, it returns #REF!

You have to write :

=INDIRECT("R1C1";FAUX)

Any ideas ?

7 Replies

  • Case matters ! I didn't notice this before : Excel in French =INDIRECT("L1C1";FAUX) results in the error #REF! Excel in French =INDIRECT("l1C1";FAUX) results in value from A1 Best regards. Daniel
    • Anonymous's avatar
      Anonymous

      Hi Daniel,

       

      the problem is solved on my installs with the latest update of Excel 2016 to Build 16.0.7341.2021 (Office Insider Slow) and Z1S1 and L1C1 are working as expected again. Thanks, MS :-)

       

      Best Regards,

      Mourad

      • Daniel Colardelle's avatar
        Daniel Colardelle
        Copper Contributor

        Hi Mourad,

         

        Thanks. I pass this to my user. I also invited him to subscribe to the Ofice Insider Program.

         

        Best regards

        Daniel

  • Anonymous's avatar
    Anonymous

    Hi Daniel,

     

    I tried following cases in an Excel 2016 Build 16.0.7167.2040 Insider Version:

     

    Excel in English =INDIRECT("R1C1";FALSE) results in value from A1
    Excel in German  =INDIREKT("Z1S1";FALSCH) results in the error #BEZUG! meaning #REF!
    Excel in German =INDIREKT("R1C1";FALSCH) results in the error #BEZUG! meaning #REF!
    Excel in French  =INDIRECT("L1C1";FAUX) results in the error #REF!
    Excel in French =INDIRECT("R1C1";FAUX) results in value from A1

    So, I see the same problem as you and I think there is something wrong.

     

    Best Regards,
    Mourad

      • Anonymous's avatar
        Anonymous

        Hi Daniel,

         

        I have posted the problem to the http://answers.microsoft.com/en-us/office/forum/office_insider-excel/indirect-function-is-broken-at-least-for-excel-in/1fcbcf20-a103-4172-abf1-2c0dfe848e60 with back reference to this thread. Yes, let's hope, it will be fixed :-)

         

        Best Regards,

        Mourad

Resources