Hi mikeh and DrBix,

I am experiencing the same issue as you are describing.  I have a repository to which I have added about 60 formatted records.  I wish to give another group of users the ability to edit or add records, but wish to be able to moderate their edits. 

My initial thought was to duplicate the page with the repository module (Page A) onto a new page which only the select users could see (Page B).  I would then allow the users to make changes to the records on Page B and I would go in and review their edits.  If all looked well, I could then swap the pages, making Page B visible to all, push the changes over to Page A and have Page A become the new 'staging' page. 

I have delved into the database to attempt to come up with a potential solution with no better results.  The problem seems to be that when you either Add Existing Module or Add Page and select to copy modules/content from another page the (I believe) core functionality of DNN (I am using 4.0.1) is to merely add new records to the TabModules table which reference the original ModuleIDs.  Therefore all you are doing is adding additional pointers to the original.  This is why when you make changes to the module on one page, it is reflected on the other.

I was looking into what it would take to script a DuplicatePage function in SQL, but there are at least a dozen tables, maybe closer to two dozen, which would all need to be updated.  If I am able to accomplish this undertaking, I will post my scripts for you, but right now I am too busy to write it.

Good luck,

Long Hair Hippie Freak