I uncovered an issue in 10.1 that may be an issue to some. If one does a FILELOCK and then opens the File again then the File Lock is dropped. This may occur where some one has the file variables in common, and may open the file again in a subroutine, where they are unsure if the File had been previously been opened.
This would not be picked up in testing, but could cause errors in file updates because the file is no longer locked someone else could update it at the time. I detected this because I was doing Transaction processing and the file was reopened due to a bug with FILEINFO function. This caused a Fatal due to records not having the right Lock levels. I have a case open with IBM, but this may be an issue for others to check their software. (This occurred on Windows 2003 and in PICK Flavour) Regards David Jordan -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
