At 08:27 AM 05 23, 2000 -0400, you wrote:
>Can you send me (not the list) your executable/dll and we can try to debug
>it from here.
Thanks for the offer, Ian, but I figured it out myself. The lock error messages
weren't referring to the line they were referring to the x&y channels, from which I
decided where to split the line.
As usual, when things seem to not make sense it's because you are on the wrong track,
not because they don't make sense.
However this leads to a feature request, how about a function which identifies whether
an object is locked, and in what mode? And another function that cycles through all
locked objects, so that they can be freed? Although neither of these would accomplish
much in terms of getting things done, they would go a long way to solving those pesky
"gx finished and left 1 locks on database" warnings.
Thanks again,
Marc
---------------------------------------------------------------------------
Data Donkey - Geophysical Data Processing, Consulting and Software Development
Creator of the POWER TOOLBOX utilities for OASIS montaj
contact: mailto:[EMAIL PROTECTED] tel (306) 931-6853 or http://www.datadonkey.com
_______________________________________________________
More mailing list info http://www.geosoft.com/support/listserv/index.html
