How to access a custom table

Please can any one let me know how to acces,update a custom table by using a LLCONNECT object in LAPI code?An example woule be handy.Thanks,

Find more posts tagged with

Comments

Appu_Nair

is the custom table in the livelink schema.If so you could write a live report and use the lapi live report sdk example to get at it.At least that is how I would write it.If the tables is vailable to you via odbc or jdbc then you probably not need lapi as well.

Appu_Nair

this is the example I would usehttps://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=3728655&objAction=ArticleView&viewType=1

Support_Lloyds_Register

thanks for this, but where is the name of the table mentioned in the Runreport() function? I mean how should i tell LAPI that I want to retrieve the data from XYZ table?Also let me know what command i should use to update the current table values?Thanks

Appu_Nair

I am not sure how you would use the LLCONNECT object to get at what you are asking.I do not think that it will be secure to call direct database queries of any nature into livelink so what the OT example does is this.Somebody has created a livereport that looks like the attachment I have.When you add it into livelink on their code its objid is 2059.It is akin to something like select name ,dataid from dtree where userid=%1That is your sql statment and the bind var or parametersSo what they are showing is the result set parsing.I was merely mentioning that by using an update statement in that LR you could do it theoretically.For that on the design of the LR you mention that it involves "database Modification".Many livelink administrators including me would shirk at running live reports that include database table modification but theoretically it is possible.(BTW I did not test an update query)In many cases updating tables in livelink probably does not get what you want most of the time lapi code when used with a correct object method updates many tables at one call.Post your correct requirement here and somebody will be telling you how the solution could be architected.

Philip Forshaw

Hi, I imagine the ability to run any SQL from outside Livelink (in this case through LAPI) was considered too much of a security risk.I get around the problem by creating a series of LiveReports available only to Admin, and execute them from LAPI.Philip Forshaw