|
Aaron:
On
quick inspection, this wrapper does not appear to be well written, or described.
For instance, as written it will not work on compressed databases. The problem
you were having with the number of values to write relates to an improperly
handled condition inside the wrapper.
My
recommendation is that for now you stick with GetChanVV_DB to get the full VV
from the channel, use functions such as Copy2_VV to set parts of it, and then
use PutChanVV_DB to set it back into the channel.
We
will have to deal with this function (which was introduced in v5.1.1)
internally, and may have to remove it or rename it...
For
now, avoid using either PutVaChanVV_DB or GetVaChanVV_DB.
_______________
Geosoft Inc.
Stephen
Cheesman
[EMAIL PROTECTED]
(905) 315-8207
Software and
services for effective earth science decision-making.
Free Oasis montaj
interface now available at http://www.geosoft.com
Hi,
Can anyone tell me the proper use of
PutVaChanVV_DB? I have a VV that I'm trying to copy to a channel starting at a
given fiducial. In particular, I'm not fully sure what the last two arguments
'offset & number to write' are supposed to be. I'm assuming offset is the
fid at where you want to start copying. Number to write is virtually a total
guess on my part, alythough I've been experimenting with it.
Here's what I've been doing:
PutVaChanVV_DB(Data, Line, Chan, hVV, 82,
iLength(hVV));
where 82 is the fid where I want to start
copying the VV to the channel and In my experience, if the last argument is
less than iLengthVV(hVV), it crashes.
Aaron Balasch
Sky Hunter Technologies
Inc.
Suite 101, 1725 10th Avenue S.W.
Calgary, Alberta T3C 0K1
email:
[EMAIL PROTECTED]
phone:
403-228-2175
fax: 403-244-7955
| 