0 Replies Latest reply on Dec 21, 2012 6:33 PM by barefootguru

    Using FileMaker with SAS via ODBC works in FMSA10 but not 12

    barefootguru

      Title

      Using FileMaker with SAS via ODBC works in FMSA10 but not 12

      Your post

           Hi, we have a SAS to FileMaker Server Advanced 10 ODBC connection which is working in our current setup, but fails on the FileMaker Server Advanced 12 machine we're wanting to commission.

           The existing working setup is:  SAS 9.3 TS1M1 32-bit, ODBC driver DataDirect 32-BIT SequeLink 5.5, FileMaker Server 10 Advanced 32-bit 10.0.2.206

           The new setup which is failing is:  SAS 9.3 TS1M2 64-bit, FileMaker ODBC driver 12.3.103.0 64-bit, FileMaker Server 12 Advanced 12.0.3.327 64-bit

           I've been working through this with SAS Institute and running some traces, and we now have a question for the FM folks:

            

           
                The trace shows that a problem occurs when FileMaker Pro 12 is meant to return the results for the "ODBC: ENTER SQLColAttribute" call SAS makes. In the old environment we can see that the call works fine and it returns "ODBC: EXIT SQLColAttribute with return code 0 (SQL_SUCCESS)". In the new environment we can see that it returns "ODBC: EXIT SQLColAttribute with return code -2 (SQL_INVALID_HANDLE)".
           
                 
           
                I find it interesting to see for instance in the call just before the failing call the following:
           
                ODBC: EXIT SQLDescribeCol with return code 0 (SQL_SUCCESS)
           
                            0x000000000044ad80
           
                                             1
           
                            0x000000000bbd8774 [       9] "TABLE_CAT"
           
                                           129
           
                            0x000000000bbd87f6 (9)
           
                            0x000000000bbd87f8 (12) <SQL_VARCHAR>
           
                            0x000000000bbd8800 (255)
           
                            0x000000000bbd8808 (0)
           
                            0x000000000bbd880a (1)
           
                In the old setup it shows:
           
                ODBC: EXIT SQLDescribeCol with return code 0 (SQL_SUCCESS)
           
                            0x02acab00
           
                                     1
           
                            0x0bc0eaf4 [       9] "TABLE_CAT"
           
                                   129
           
                            0x0bc0eb76 (9)
           
                            0x0bc0eb78 (12) <SQL_VARCHAR>
           
                            0x0bc0eb7c (128)
           
                            0x0bc0eb80 (0)
           
                            0x0bc0eb82 (1)
           
                The 128 vs 255 is interesting. You can find the definition of the call and it's values here: http://msdn.microsoft.com/en-us/library/windows/desktop/ms716289(v=vs.85).aspx. I can see that the 255 and 128 is "SQLULEN *      ColumnSizePtr". It would be good if you can involve FileMaker support to have a look at the trace and ask for their input.
           Thanks.