Thanks for your reply.  The upper level shared folder was already there and with permisions on it.  All I done was copy more folders with files under those folders from an NT 4 Server over to this shared folder on the 2003 Server.  I didn't have to change any permissions because they were already set.  I have change and read permissions the users that access the shared folder and subfolders.  Any files and folders that were copied form the NT 4 Server cannot be deleted by the users accessing them.  They can modify and save them with no problem, just cannot delete them from Windows Explorer, however, any new files created into these folders can be deleted with no problem.

Thats because new files/directories have all of the correct permissions set (as expected since they were created in place).  The fact the moved items are not deletable means there is some kind of a problem with the permissions as currently set.

If you go to the top level directory and make a change to the permissions and have it cascade down through all the subdirectories, then go through and change the permissions back (if you changed them away from what they should have been) then it should fix the problem.  I've run into this before on a Win2K server that had files moved to it from both another 2K system and an NT4 system, and doing the cascading/recursive permission changes (telling it to change/set the permissions on all subdirectories and files) fixed the problem at the time.

The other option was to go in and individually reset the permissions on each file and directory.