Inconsistent Object References

I encountered a problem with a module I created. In the module I reference another object in the another module using the:Object obj = #9999999Everything worked fine on my laptop and on the staging server, but when I moved my code to production, the object was never getting initialized correctly because the object reference was different on production. Further looking into revealed that a lot of the object references are different. This should NEVER be the case. The object references are how you are told to reference and should remain consistent no matter what instance or platform I am running Livelink. I corrected my problem, but has anyone else encountered this? Is there a way that I can get my production server and the test server in sync so I don't run into these issues elsewhere?

Find more posts tagged with

Comments

eLink User

Message from Hans Stoop <<A HREF="mailto:hstoop@opentext.com">hstoop@opentext.com> via eLink

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">eLink

Hi,

It is not a good thing to use the numbers directly. Always use global variables that are initilized during Livelink startup. You can also let object reference eachother by creating features that point to them. That mechanism is used when you do an 'Add To Globals'. Livelink will update thease feature with the correct object reference.

Hans Stoop

----------------------
LivelinkUp Europe 2002
Open Text User Conference
Paris, France
April 14-17, 2002

Find out how we're helping five million great minds
work together to improve efficiencies and save money.

http://www.opentext.com/livelinkup/

-----Original Message-----
From: knowledge@opentext.com [mailto:knowledge@opentext.com]On Behalf Of eLink Discussion: Development Discussion
Sent: dinsdag 19 februari 2002 17:35
To: eLink Recipient
Subject: Inconsistent Object References

Inconsistent Object References Posted by BaeAdmin (Sutterley, George) on 02/19/2002 11:33 AM

I encountered a problem with a module I created. In the module I reference another object in the another module using the:

Object obj = #9999999

Everything worked fine on my laptop and on the staging server, but when I moved my code to production, the object was never getting initialized correctly because the object reference was different on production. Further looking into revealed that a lot of the object references are different. This should NEVER be the case. The object references are how you are told to reference and should remain consistent no matter what instance or platform I am running Livelink.

I corrected my problem, but has anyone else encountered this? Is there a way that I can get my production server and the test server in sync so I don't run into these issues elsewhere?