some background: i'm upgrading from PB8 to PB12.1 (Build 6639). Oracle 10g is the database; Oracle 11g client.
At issue are our forms, which are ANSI RichTextFiles (RTFs)
stored as Binary Large Objects (BLOBs) in the database.
When I edit the forms (display them in an rte control), PB12
automatically converts them to the UNICODE standard, (via
CopyRTF, EncodingANSI!). Through the assistance of a PB
Help Desk call, I was able to successfully create/edit text
only documents. (the solution was to set my DBParm
"NLS_Charset='Local',StrByCharset=1")
However, erratic behavior occurs when I try to add
parameters, (i.e., mailing name, address, etc.) to the (now)
UNICODE forms. The expected behavior is for the parameter
to be added where the cursor is positioned. In practice,
this may or may not occur. I’ve seen the parameter
inserted above or below or even above and at the location of
the cursor (an insert to 2 places at the same time).
Also, it seems a parameter label should be stored in the RTF
and sometimes it is not. what i see is:
{\*\txfieldtext ?? {\*\txfieldend}}??
When asked to print, my application code looks for this
label in the form and uses it to insert data. If the label
isn’t found, the substitution cannot occur.
Has anyone else experienced this behavior and, more
importantly, does anyone have a solution or work-around?
i've tried posting this same question on Sybase's forum, but have not received any response.
thank you.
At issue are our forms, which are ANSI RichTextFiles (RTFs)
stored as Binary Large Objects (BLOBs) in the database.
When I edit the forms (display them in an rte control), PB12
automatically converts them to the UNICODE standard, (via
CopyRTF, EncodingANSI!). Through the assistance of a PB
Help Desk call, I was able to successfully create/edit text
only documents. (the solution was to set my DBParm
"NLS_Charset='Local',StrByCharset=1")
However, erratic behavior occurs when I try to add
parameters, (i.e., mailing name, address, etc.) to the (now)
UNICODE forms. The expected behavior is for the parameter
to be added where the cursor is positioned. In practice,
this may or may not occur. I’ve seen the parameter
inserted above or below or even above and at the location of
the cursor (an insert to 2 places at the same time).
Also, it seems a parameter label should be stored in the RTF
and sometimes it is not. what i see is:
{\*\txfieldtext ?? {\*\txfieldend}}??
When asked to print, my application code looks for this
label in the form and uses it to insert data. If the label
isn’t found, the substitution cannot occur.
Has anyone else experienced this behavior and, more
importantly, does anyone have a solution or work-around?
i've tried posting this same question on Sybase's forum, but have not received any response.
thank you.