** ?
Ive done this before mainly to store offline tickets in another database and still have it present itself in the production system and it thinks its a local form. You will only need your point your local view at the remote view.
 
here the view syntax to use the dbms_lob procedure
 
 
SELECT T325.C1,C2,C3,C4,C5,C6,C7,C8,C112,C61261235,C200000003,
    C200000004,C200000005,C200000006,C200000007,C200000012,
    C230000009,dbms_lob.substr(C230000010,4000,1),C240000000,C240000001,C240000002,
    C240000003,C240000005,C240000006,dbms_lob.substr(C240000007,4000,1),dbms_lob.substr(C240000008,4000,1),
    C240000009,C240000010,C240000011,dbms_lob.substr(C240000012,4000,1),C240000015,
    C240000016,C240000017,C250000007,C250000010,C250000011,
    C250000012,C250000013,C250000014,C250000015,C250000016,
    C250000017,C250000018,C250000021,C250000022,C250000023,
    C250000030,C250000031,C250000032,C250000050,C260000000,
    C260000004,C260000005,C260000006,C260000100,C260000101,
    C260000123,C260000126,C260000127,C260000128,C260000129,
    C260000130,C260000131,C260000133,C536870922,C536870923,
    C536870924,C536870925,C536870928,C536870932,C536870935,
    C536870936,C536870941,C536870942,C536870943,C536870944,
    C536870945,C536870946,C536870963,C536870964,C536870965,
    C536870967,C536870968,C536870969,C536870971,C536870972,
    C536870973,C536870974,C536870975,C536870976,dbms_lob.substr(C536870977,4000,1),
    C536870978,dbms_lob.substr(C536870981,4000,1),
    dbms_lob.substr(C536870982,4000,1),C536870984,C536870985,
    C536870986,C536870987,C536870988,C536870989,C536870993,
    C536871009,C536871012,C536871014,C536871015,C536871017,
    C536871023,C536871025,C536871032,C536871038,C536871039,
    C536871041,C536871044,C536871045,C536871046,C536871049,
    C536871050,C536871055,C536871056,C536871057,C536871058,
    C536871059,dbms_lob.substr(C536871060,4000,1),C536871061,C536871062,C536871063,
    C536871064,C536871065,C536871067,C536871069,C536871070,
    C536871071,C536871072,dbms_lob.substr(C536871073,4000,1),C536871074,C536871075,
    C536871076,C536871077,C536871078,C536871079,C536871080,
    C536871081,dbms_lob.substr(C536871082,4000,1),C536871088,C536871094,C536871098,
    C536871103,C536871104,C536871105,C536871106,C536871107,
    C536871110,C612612001,C612612003,C612612006,C612612007,
    C612612010,C612612026,C612612030,C612612044,C612612046,
    C612612047,C612612057,C612612076,C612612077,C612612078,
    C612612079,C612612080,C612612081,C612612082,C612612083,
    C612612086,C612612087,C612612091,C612612092,C612612110,
    C612612117
    FROM T325
 
 
Hope it helps
 
Greg Elphick


From: "Action Request System discussion list(ARSList)" <[email protected]> [mailto:"Action Request System discussion list(ARSList)" <[email protected]>] On Behalf Of Mike Gould <[EMAIL PROTECTED]>
Sent: Wednesday, 24 January 2007 8:00 AM
To: [email protected]
Subject: Accessing CLOB Datatype via Oracle DBLink in View Form

**
Hi Gang,
 
I'm getting an error when I try to add a CLOB field to a View Form that is accessing a remote table via an Oracle database link.  It looks like Oracle doesn't support this functionality in database links.
 
Has anyone figured out a method to expose a remote database's CLOB data in a View Form?
 
Thanks in Advance,
Mike Gould
US House of Representatives
 
AR System 7.0.01
Solaris 9
Oracle 10gR2
__20060125_______________________This posting was submitted with HTML in it___

--

This transmission is for the intended addressee only and is confidential information. If you have received this transmission in error, please notify the sender and delete the transmission. The contents of this e-mail are the opinion of the writer only and are not endorsed by the Mincom Group of companies unless expressly stated otherwise.

--

 

 

 

 

 

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to