In My Humble Opinion (don't laugh people), ODA is a poor choice for database access by a program (VB?). ODA has several problems that I won't re-iterate here (if you want my opinions on ODA problems search the archives).
I suggest that you create views in your DBMS that contain the data you need and have your program go directly against those views - bypassing ODA/OneWorld.
Larry Jones [email protected]
OneWorld B733.1, SP 11.3
HPUX 11, Oracle SE 8.1.6
SandBox: OneWorld XE SP15
I got a problem when working with ODA. Let me explain it to you:
I have an enterprise server that uses Oracle as database and I want to get information from it using ODA. I saw documentation about how having ODA enabled when using Oracle. Actually I have gotten information from many different files. However, when I set up row security for some files (F41001, F006), it seems like ODA does not take row security into account. The only condition for row security to work properly is:
Having global tables deleted before running a query AND simultaneously using the restricted columns as filters for such query.
Otherwise, I am able to see all the information from the files, even if I have row security. For example: I can see Cost Center Column (MCU) in Inventory Constants File (F41001), even if I restricted not to view Cost Centers in range from " 10" through
Does anybody have any comments about it?
I hope you can help me...
Thanks a bunch