Topic:
Why do my markers not post at the correct time after changing assocaited checkshots?

Description:
In this particular instance, after associating the borehole to a checkshot for 
the first time, the user generated the seismic time pick values for those 
markers.  Then, when the borehole was associated to a different checkshot, the 
markers posted on the seismic at the same time as they did with the first 
checkshot.

Solution:
When the seismic time picks for markers are generated in GeoFrame, they are 
essentially left as such in the database until they are manually changed.  
Therefore, by merely changing the borehole's associated checkshot, the seismic 
time picks will not change, hence they will not post as such on the seismic.  To 
post the marker times based on the currently associated checkshot consider the 
following options:

1.) After associating the borehole to a new checkshot, go into the project
marker data manager and 'convert to' seismic time pick.  The conversion will 
write over the existing seismic time picks with the two way time picks of the 
currently associated checkshot.

2.) In the project marker data manager, change all the seismic time picks to a 
value of 0 or -999.25 (null value).  This way, the seismic time pick is not hard 
coded based on the conversion done in #1 above, and when there is a change in 
the associated checkshot, the seismic display will reflect the changes.

3.) Rather than 'hand edit' the seismic time picks like in #2 above, use SQL to 
change all the seismic time picks to -999.25 in the oracle database:
in a GeoFrame xterm: 
'sqlplus project/password'
SQL> update well_marker set TIME_PICK = -999.25;



NOTE: In order for a marker to post in GeoViz, the Seismic Time Pick must be 
calculated.  Therefore, 2 and 3 above will not post the markers in GeoViz.




Last Modified on: 04-MAY-99