Making a read only client file, is it possible if I have a client file that is read write?

Here is my situation. There are 6 of us using a split database. The database is located on our server in a folder, from there it is split into to more folders. Folder one is the client file folder containing the client file (The nav and reports etc.) the second folder is the database (containing multiple tables with the data we enter from the forms in the client file). Things have been working great until recently our financial controler has just started using the database and our data has begun to disappear. Just so no one asks, yes it is because of her, the entire team has witnessed it at some point or the other, she highlights and copies but doesn't pay attention to what she is doing and cuts or deletes data out of the forms while going through the files. I created queries for her with all the data but she wont use them because it and I quote, "doesn't look as pretty as the form and she prefers the form view." Our boss has told her to use them and she still doesn't even though she says she is, I know she isn't becuase our data continues to be deleted. My solution would be to fire her as access and excel do her job for us but thats another story.

What I want to do is create another client file solely for her that only gives her the option of the queries and nothing else, strictly read access no write. Is this possible or is there another way to do this? Do I have to create a user login is that the only way?

Yeah I looked for that as i remember that being and option at some point but i couldn't find it on this database. I think I'm going to have to create a login process which i haven't done in a few years and can't for the life of me remember how to do it or how to set user access to only certain options. I was hoping for someone to say just make a second client file by doing this this and this and have her only use that file, sadly I don' think thats possible.

lol Thank you for the support. I thought i had actually figured it out but I'm now having issues with client files over writing each other. So two seperate client files didn't work. Locking her out of the ability to write to the file didn't work as access 2010 wont allow you to enter the file unless you have both. I then found out that the directions that I sent out about copying the shortcut created to access the client file she didn't even read and just copied the entire client file folder, this has led to some odd situations as the path has changed of the client file that she copied to her machine and it is overriding the actual client file and when she got into the the client file she copied it brought her into edit mode and she clicked a few things here and there and deleted half the client file reports and queries. It took 2 weeks to figure that out as she kept lying and saying she did what the directions stated. Thank god for regular backups, I have no idea how she managed all that in such a short period of time. Basicially I'm still looking at ways to get two client files to access the same database or spending the contract hours to build a user interface. Which I assume isn't hard but I haven't done that in a very long time and it would take a lot of reading up on things so I can do it again. Why can't they just not mess up the files lol