Thanks for your response.
In the original code, assigning
$sql
was done by a subroutine:
sub build_sql { #process args; return $sql_block; } $sql = build_sql ( \@layout, \%myfilter );
However, in the interests of testing, I simpy did it like this:
$sql = qq { set quoted_identifier on use "smdb"; set TRANSACTION ISOLATION LEVEL READ UNCOMMITTED; SELECT "_SMDBA_"."_TELMASTE_".SEQUENCE AS "Problem #", "_SMDBA_"."_CUSTOMER_".FNAME + ' ' + "_SMDBA_"."_CUSTOMER_".NAME AS "N +ame", "_SMDBA_"."_CUSTOMER_".EXT AS "Cl. Ext", "_SMDBA_"."_TELMASTE_"."DESCRIPTION" AS "Problem Description", "_SMDBA_"."_TELMASTE_"."DATE OPEN" AS "Opened", "_SMDBA_"."_PERSONNEL_".CODE AS "Assigned To" FROM "_SMDBA_"."_CUSTOMER_","_SMDBA_"."_TELMASTE_","_SMDBA_"."_PERSONN +EL_" WHERE "_SMDBA_"."_TELMASTE_"."SENT TO" = "_SMDBA_"."_PERSONNEL_".SEQUE +NCE AND "_SMDBA_"."_TELMASTE_".CLIENT = "_SMDBA_"."_CUSTOMER_".SEQUENCE AND "_SMDBA_"."_PERSONNEL_".CODE LIKE 'MUSER' AND "_SMDBA_"."_TELMASTE_".STATUS = 'O' ORDER BY "Problem #"; };
The SQL may look a little hacky, but I didn't design the DB :) It's basically to select various fields related to open helpdesk calls from several tables. (I have tried a simpler select from a table within that database, and that fails with exactly the same problem)

Having looked at eval, and trying it, I unfortunately get almost exactly the same response: $trans_handle -> execute does not return any value. (This was at the same time as setting 'RaiseError' and 'PrintError' to 1).

Whether that means that it is only executing one of the 'set' commands (which is possible, but even when I remove them I still don't get any errors) I don't know.

I still think that 'selecting' the database, and enabling the quoted identifiers is what's failing, but I can't figure out how/why they aren't setting properly.


In reply to Re: Re: DBD::Sybase + MS SQL server problem by Preceptor
in thread DBD::Sybase + MS SQL server problem by Preceptor

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.