In response to a bug report from Peter, I have made some changes to NDF
at a pretty low level. Needless to say you should all be on the look out
for strange behaviour as a consequence. The changes are:
1) When writing a native NDF to a foreign format file, any existing
foreign file is now not deleted if no conversion command has been defined
for the format. Previously, it deleted the existing file and then said
"Oh, in fact I dont know how to create a new one. Sorry!".
2) If you import a forign format NDF with READ access and then get a
locator to the temporary HDS file and re-import that as a native NDF,
also with READ access, AND if the temporary HDS container file has write
access, then the access to the original NDF was previously upgraded to
UPDATE, resulting in an attempt to write out the contents of the NDF when
the NDF was closed. This has been changed so the access to the *foreign*
file rather than the HDS file is used to determine the access available
through any NDF identifier associated with the temporary HDS object.
Got that??
David
|