Howdy y'all! I'm trying to get Sybase::CTlib working so I can write an interface for a third party we're dealing with. My first shot at Sybase::CTlib. No matter what I do it seems, I get:

Server message: Message number: 208, Severity 16, State 1, Line 1 Server 'ADS' Message String: Edition not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output).

These tables exist, and with isql the queries run.

I'm using a simple query to learn the ropes with this:

#!/usr/local/bin/perl -w use strict; #use Date::Manip; use Sybase::CTlib; my $restype = ""; my $edition = ""; my $dbh = new Sybase::CTlib 'uid', 'pwd', 'ads', { CON_PROPS => { CS_SYB_CHARSET => 'utf8bin'} }; my @dat =$dbh->ct_sql("select code from Edition"); print @dat;

Being newest to it, I'd appreciate any and all help I can get! Thanks.


In reply to Sybase::CTlib errors by plockhart

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.