>>A little off the subject of this post, but related. On a Novell file system >we give permissions to certain people down to the file level. Some have >permission to read files in a directory, but there are 2 files in the >directory that the people are allowed to update. So I instruct Novell to give >this certain group Read/Modify on these to VFP tables. Well when the >administrator does a PACK (which is done regularly) the VFP Pack command does >what you describe above. The original files dissappears and is brought back >with the records not marked for deletion. What happens is that Novell senses >that the files are gone and guess what. So is the permissions for that group >to Read/Modify those 2 files. Does anyone know a work around for this or a >way to tell Novell to maintain the permission even if the file dissappears >during a VFP pack?
>
>
>
>Would the following be a viable solution for you? I just tried the following with W2K and ZAPing didn't change the permissions, maybe it would work with Novell too...
>
>Instead of PACKing the table, write a utility/routine that will create a copy of the table, ZAP the original, then append the records from the copy (for not deleted) back into the original table... or just PACK the copy and append back...
>
>Granted it's crude, but it's an idea.
>
>
>- Brian


Crude, but might just work. I will put it out as a suggestion for those special tables. Thanks for the suggestion.