Regarding We're going to need a bit more detail.

For problem 1:
Q: What does the schema look like?
A: So far, all reported problems have been with fields that are varchar in the database. The smallest 500varchar, the largest 2000varchar. In trying to recreate the problems in our test environment, I get the problem when I use strings with 40+ characters and end the string with 1 or more spaces. When I use short stings ending in space, it often works (“A “ doesn’t cause a problem.)

Table DIRprcom(Provider Comments)

pr_id   1   varchar(9) /Key
pr_id_suf   2   varchar(6)
pr_comment  3   varchar(2000)  /Problem field.

pr_comuid   4   varchar(8)
pr_comudt   5   timestamp

SQL Anywhere stores precisely what you give it, regardless of interface and regardless of whether or not the database is blank-padded or if the field is CHAR or VARCHAR. Unlike ASE, SQL Anywhere will also store trailing blanks and these are an inherent part of the value.

For problem 2:
Q: What is the data type used for the column?
A: I declare it as decimal in my Powerscript and in my db stored proc.

Q:How are you fetching it in your Java application?
A: I initialize it to 0 then I call the stored proc from my Powerscript.

// Start PowerScript code snippet
// Adjudicate each line item & calculate line item payable amount.

decimal     lc_line_payable_amt…
//lc_line_payable_amt = 0.00   this line will get around the problem if the following line is commented out.

lc_line_payable_amt = 0
    …
// call stored proc
SQLCA.adj_line( gs_usertype,    &…
lc_line_payable_amt, &…
)…
// End PowerScript code snippet
// When using ODBC, returns accurate payable amount if payable amount contains cents.  If switched to JDBC, lc_line_payable_amt rounds to nearest whole dollar.

For problem 3:
Q: When you say "Does not work", what do you mean? Do you get an error?
A: I will need to collect the specific info. //We can work around this.

Problem 2: Can you expand this a bit more? I am unable to see this problem with a datawindow or the following powerscript code:

decimal{2} v;

declare foo_proc procedure for foo using sqlca; execute foo_proc; fetch foo_proc into :v;

calling a procedure defined as

CREATE PROCEDURE "DBA"."foo"( ) BEGIN declare v decimal (5,2); set v = 1.23; select v from dummy; END

Problem 3: I am able to get this code to work with both JDBC and ODBC connections. What specifically do you mean by "not work"? Can you check for errors ( trans_obj.SQLErrText ) after each statement? Here is the code that I am testing:

// Grant connect, resource, and membership privileges to the new user // while we have dba privileges. string sql string userid = "u" string pwd = "p" string grp = "g"

if( rb_1.checked ) then userid += "_jdbc" else userid += "_odbc" end if

sql = "grant connect to " + userid + " identified by " + pwd execute immediate :sql using sqlca; if( sqlca.SQLCode <> 0 ) then MessageBox( "User creation error", sqlca.SQLErrText ) end if

sql = "grant resource to " + userid execute immediate :sql using sqlca;

sql = "grant membership in group " + grp + " to " + userid execute immediate :sql using sqlca;