Recent content by jpickup

You'll need a bind variable for the result and or inputs instead of locally declared variables whose contents are not available outside the scope of the PL/SQL.

Look at TOracleSession.Preferences.TrimStringFields

Look at TOracleSession.Preferences.ConvertCRLF

If you explicitly select the rowid and alias it then it is accessible. For example SELECT rowid AS UniqueID, ...

Each thread must have its own session. This must be a real Oracle Session and not just a TOracleSession component that is sharing another component's session (i.e. no use of the Share method or the Externalxxx properties)

Look at the properties Master and MasterFields. They provide the master/detail behaviour you require.

The problem is with the Fields set up in the OracleDataSet. If no fields are setup then you see all from the query BUT as soon as you define a field (in this case the calculated one) then only those defined are seen. So, since you are adding a field you will need to add other other fields that...

I could not believe the 'I don't know if this is possible' as in Delphi, anything possible at design-time is also possible at run-time. So, created a project with an OracleSession, OracleDataSource, DataSet and DBGrid. Added the following to a button and it works (is identical to the code...

select "package" from items (package is a reserved word so you need quotation marks to make it a literal) [This message has been edited by jpickup (edited 17 September 2002).]

Thanks - that works. Presumably this is what the share method does internally. [This message has been edited by jpickup (edited 15 August 2002).]

I can't seem to use TOracleEvent with sessions that have been shared using the ExternalSVC property. They do however work with sessions shared with the Share method. Other DOA components (TOracleQuery & TOracleDataset) work fine with the ExternalSVC approach. Example: Drop two TOracleSession...

Are you commiting the transaction (Commit method of TOracleSession)?

it'll probably be easier not to use a cursor in this situation (I assume you've got a cursor with something like 'select * from options'). If instead you dynamically build 'select option1 from options', etc. in a loop then the earlier example should work. But, I would create another table so...

The example given is clearly not complete. For one thing you would need to declare a variable V of the appropriate type based on your table definition. The technique does work, perhaps you should familiarise yourself with it using some simpler examples. Your database design should be improved...

You could always use dbms_sql or execute immediate. e.g. For i in 1..4 loop gp:='select pollquestion_rec.Option' | | i | | ' from dual'; execute immediate gp into v; htp.p(v); htp.p(' '); end loop;