How to retain the Object ID as reference type?

Support_Lloyds_Register

Hi All,I have a small query.I have the following function definition in VB:dim Object_ID as Integer = 0public function Test1()errStatus = LL_CreateObject(Session_ID, Volume_ID, Parent_ID, LL_OBJECTTYPE, Object_Type, DocName, objInfo)Status = LL_AssocGetInteger(objInfo, "ID", Object_ID)end functionThe newly created object's ID is copied into "Object_ID".The definition of LL_AssocGetInteger(objInfo, "ID", Object_ID) says that the parameter "Object_ID is of reference type. So it means that we can use this variable in other custom functions without reinitializing it. for example as below:public function Test2()errStatus = LL_CopyObject(Session_ID, Volume_ID, Object_ID, DstVolume, DstObject, LL_COPY_CURRENTV, DocName, Obj_Info)end functionNow, if i have to convert the entire above code in VB.NET we use as follows :public function Test1()objInfo = New LLValue().setAssocNotSet()errStatus = docInfo.CreateObject(Volume_ID, Parent_ID, LAPI_DOCUMENTS.OBJECTTYPE, Object_Type, DocName, objInfo)Object_ID= objInfo.toInteger("ID")end functionNow my query is can we use "Object_ID" as reference type in other custom defined functions in VB.NET ( below example)just like its used in the VB part?public function Test2()errstatus=docInfo.CopyObject(Volume_ID,Object_ID,DstVolume.....)end functionDoes the above Copy function take the Object_ID as 0 or the current value of Object_ID ?If it takes 0, can u please let me know as how to retain the newly created id??Regards,

Todd_Pinel

This is more of a general programming question rather than a Livelink specific one. This question concerns the difference between VB and VB.NET and some Object Oriented Programming.It looks like in your original VB code someone was setting a global value that they were wanting to use anywhere else they wanted to. I've never liked this approach and in the OOP world of VB.NET you could get a similar effect with the following code:Public Class Test Private _testObjectId As Integer Public Property TestObjectId() As Integer Get Return _testObjectId End Get Set(ByVal value As Integer) _testObjectId = value End Set End Property Public Function Test1() Dim objInfo Dim errStatus objInfo = New LLValue().setAssocNotSet() errStatus = docInfo.CreateObject(Volume_ID, Parent_ID, LAPI_DOCUMENTS.OBJECTTYPE, Object_Type, DocName, objInfo) Me.TestObjectId = objInfo.toInteger("ID") End Function Public Function Test2() Dim errstatus errstatus = docInfo.CopyObject(Volume_ID,Me.TestObjectId,DstVolume.....) End FunctionEnd ClassYou'll have to clean this code up and I would not suggest maintaining the ObjectID this way. I would create 2 functions. One function that created the object and returned the ObjectID as a result. The second function would accept an ObjectID parameter (which could be taken from the result of the first function) and then other parameters indicating the remaining information required to complete the LAPI copyobject method (parentid of the location, copy options etc...). This approach would give you more control over the objectID you are creating and passing around vs keeping it as a pseudo-global variable of the class that you would have to be careful managing on your own.