lastenia_rojas

Hi,

In Oracle, when ProIV populates a varchar2 col, spaces to the right of the value are trimmed. In sql server this doesn't seem to be the case for varchar cols. I was wondering if there is a config parameter in ProIV or sql server so that ProIV's behaviour on sql server matches Oracle's. Thanks.

Lastenia.

Running ProIV 5.5r518 on Windows2000, and MSSQL 2000 with latest service pack:

We intend to port a ProIV app from Oracle to MSSQL. We are currently running small ProIV functions to get a taste of the differences between the two. An issue we've found is that when we do a lscall to a ls that writes to a child table, ProIV is committing the new child records before the function completes (hence there is the possibility of ending up with orphan records if the function rollbacks after the lscall that writes the children). I suspect an incorrect pro4.ini setup is what is causing this behaviour. We are not issuing our own commits nor enabling &#@SUPP-COMM. Currently, the MSSQL database is set as the default SQL database, and we also have the following environment values defined:

SQL_CURSORS=32
SQLSERVE_SELECT_FOR_UPDATE=TRUE
SQL_TRANSACTION_ERROR=Y

We also look at a SQL trace produced by ProIV (TRACESQL=15) and confirmed that ProIV is indeed instructing MSSQL to commit the child records.

Are we missing something?

Any pointers are appreciated. Thanks!.

We want to access a MS SQL table from ProIV. The MS SQL database is the default database. Unless we specify the SQL select statement ourselves, we get an 'Invalid cursor position' error as soon as we move into any of the table columns. The function is a paging screen. Scrolling up/down works fine. Moving into any of the columns is what is causing the grief. I was wondering if other people have experienced the same problem, and if so, any info with regards to the cause of the problem and how to resolve it are greatly appreciated. Thanks.

Does anybody know if there's a way in ProIV to set the OCI_ATTR_PREFETCH_ROWS
parameter in the Oracle sql*net (or whatever is called this month) connection ?.

Thanks.

We are currently testing our ProIv application on a HPUX B.11.11 server running Oracle 9.2.0.1. What we have found so far:

- ProIV 5.0 32 bits linked to Oracle 8.1.7 32 bits Client talking to Oracle 9.2.0.1 64 bitsServer:
Decimals get dropped on big numbers when the numbers are retrieved from the database.

- ProIV 5.5 64 bits linked to Oracle 9.2.0.1 64 bits Client talking to Oracle 9.2.0.1 64 bits Server:
Random ORA-01401 (inserted value too large for column) and ORA-01722 (invalid number) errors.
Looking at Oracle trace files, Oracle is getting garbage as the value of bind variables in the sql statements
(when ORA-01401), and aborting queries at the parse stage (even before binding variables) when ORA-01722.

Has anyone else experience these behaviours with the above or similar versions of ProIV/Oracle?. We're currently in the process of
getting Oracle to the latest patch level. Thanks.