Jump to content


TomWhite

Member Since 20 Jun 2005
Offline Last Active Feb 18 2012 01:12 PM
-----

Posts I've Made

In Topic: Oracle Selection Issue

18 February 2012 - 01:11 PM

Thanks Richard for the response. We were unaware of the trace options - haven't had a chance to try that yet, but even if they don't help in this case I'm quite sure they will be invaluable going forward as we move more towards ORACLE.

Cheers

In Topic: Oracle Selection Issue

07 February 2012 - 06:32 PM

Andy,

I appreciate any and all thoughts on this, please keep them coming. That code is pretty standard for us since at one point if there was any 'leftover' data in a key beyond the selection key it would limit the data to only what was beyond that data....in essence doing a start from whatever was in that field. I'm not sure if that's no longer the case, but we've always 'cleared' data in subsequent key fields when doing a sel-only. I did try removing that line and ended up with the same results, - nothing selected.


Cheers,
Tom

In Topic: Oracle Selection Issue

07 February 2012 - 01:21 PM

No, the file is not auto-sequenced...for this particular app the data is being added directly to Oracle thru a web app and currently is just being accessed to display in an existing PROIV system.

In Topic: Oracle Selection Issue

03 February 2012 - 03:04 PM

Yes, privileges are fine...the same selection works fine in a paging screen against the view, it just doesn't work in a report or update.


Cheers.
TW

In Topic: Oracle Selection Issue

03 January 2012 - 05:59 PM

No, we've used a SQL select statement to get by this, but we are still trying to figure out why the sel-only works fine on the paging screen but not in the report.