This content has been marked as final. Show 4 replies
Up until a certain version of the OCI (and I forget exactly which version, see below) if you called the OCI initialization routines multiple times, only the first one was used.
I am pretty sure that this was fixed in one of the 8.1.7 patch releases, but I know it is fixed by 9i. The only problem still seems to be that you can only get more restrictive, not less. In this case you should be OK.
You're right - We do not have this problem on Oracle 9i, only 8.1.7 running on W2K.
I relalise that initialising OCI using OCI_THREADED is less restricive than the original OCI_DEFAULT and this causes the problem.
My problem is how can I force oo4o to initialise OCI using OCI_DEFAULT and not OCI_THREADED ?
I don't think you can. The C++ interface for OO4O allows for you to specify multi-threaded or not (which presumably means OCI_THREADED or OCI_DEFAULT) but I do not knwo of anyway to control this in a 4GL like VB/PB.
I think you proably mean the OStartup() method. This function takes a parameter to specifiy what sort of initialisation shuld be carried out.
I tried both options for calling this function, with no success.