The client wants to backup the live Adagio company data files each evening and as well, to copy all the files to a separate directory.
He can then access the copied data the next day for testing & other purposes.
My fear is that a user may access the copied data and enter live data (since it looks the same as the live data). This data is overridden that evening.
Is it possible to restrict users from accessing a separate directory from within Adagio?

Here is an idea.

In the copied folder, you will find a file for each application with a name in the form: XXwinini.yyy where XX is the applcation and yyy is your data extension. One of the settings in this file is the backround colour.

Change the background colour for all the datasets, then save a copy of the modified XXWININI files to another folder. Set up the copy routine to copy these versions of the files into the backup folder after the data copy, overwriting the ones that came from the live data folder.

Then, at least, the colour will alert the user to the fact he/she is not working in the live data.

Ralph - I like your idea. Thank you!
As you claim, this will alert the user that they are using the copy and not the live data.
Of course, if the client changes the Company Profile or for example, adds new Optional Fields, then we would lose the changes if we copy the original winini file back.
I imagine that I would have to inform the client that in case they do any Profile modifications, then we would have to reset the colours.
But this is tons better than doing nothing. I will give it a try.

Hi Samuel,

From your post it looks as though only one user wants to have access to this copied "Testing Data".

Based on that assumption, another thought would be to simply copy the "Testing Data" to his local drive in a folder that other network (another assumption) users do not have access to.

If the objective is to have multiple but limited users have access to the testing data then it should not be a problem to simply have the the network (as opposed to Adagio) security restrict access to the test folder(s).

One could still do the "colour thing" to help the specific users distinguish between the live and testing data.