OK, alvaro99, I think I did not understand your first post. There are several types of accounts in Windows 7 known as Groups. A user account may belong to one or several Groups. One such Group is Administrators. An account belonging to this Group would be labeled as administrator account and would have sufficiently more privileges compared to a standard user account.
There is however an additional, the so-called built-in Administrator account, which has nearly infinite power (it's different from the administrator accounts I just mentions and it's more powerful). This account is unique and cannot be duplicated. That's what I meant in my previous post.
Now, a solution to your particular problem is to add your user account to the administrators group. Then you could try your program and if it's still refused the ability to write into system folders, then you will have to elevate it by modifying the shortcut making it run "as administrator".
A brief explanation is the following. Windows protects system folders. Therefore "standard users" are not allowed to modify them in any way. If a standard user runs a program that needs to write in a system folder, then the system re-directs to a mirror folder called "virtualstore". On the other hands, administrators are able to modify the system folders, so if you run a program "as administrator" (i.e. with elevated privileges) then it can write to system folders directly without using the virtualstore.
Now, for most programs this is not a problem, Windows 7 manages virtualstore for them and they would not know the difference, unless the folder path where the program wants to write its data is hard coded, i.e. the developers have written the explicit path into the code. It seems that this is your situation. Again, it can be solved by running the program "as administrator".
Hope that clarifies the issue now.