HI,
Not being able to 'give' ownership to someone else is a key part of NT\win2k\xp security. The idea is that an admin or other unscrupulous user cannot take ownership of a file or folder, grant themselves access to it, then give the ownership back when they had finished. The fact that ownership would from that point belong to them means that there is a 'paper' trail that indicates what has gone on. Your users should not need ownership of a folder or file to access it anyway, as long as you have granted them permissions on the folder or file via the properties \ security tab of the file or folder in question. This also cannot be an account issue - whereby the app is set to run only under the admin account, because making your user a member of the admins group would not fix this.
What you could try is downloading regmon and filemon from sysinternals.com - which will give the result of all attempted file and registry access attempts including whether or not access was denied. run regmon while logged in as admin, then use runas (highlight the app, hold down ctrl and shift then right click) to run the problem app as the user. Once the error appears, scan the output of regmon for access denied messages to see where the access is being blocked. Next do the same thing with filemon. Once you have correctly set permissions on any file or registry areas that are flagged as problems, you should be ok. Hope this helps...