I thought of it as one of the possibilities.. thank you for your reply!

http://www.codeproject.com/Lounge.aspx?msg=3508009#xx3508009xx[^] ;P :rolleyes: ..Go Green..

Sounds like something a sledge hammer could fix quickly. :) Good luck and let us know what happened! CQ de W5ALT Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software

I dont understand why you fired button1_Click event....just fired button1_MouseClick event that's it.. Thanks Md. Marufuzzaman Don't forget to click [Vote] / [Good Answer] on the post(s) that helped you. I will not say I have failed 1000 times; I will say that I have discovered 1000 ways that can cause failure – Thomas Edison.

After 3 weeks i finally stumbled upon the cause of the problem. All my non working applications had the string "update" in their filename/assemblyname... And of course everyone (except for me) knows that the UAC recognizes the program as an installer when the string "update" is found in the filename/assemblyname. :sigh: As found on technet[^] Installer Detection Technology Installation programs are applications designed to deploy software, and most write to system directories and registry keys. These protected system locations are typically writeable only by an administrator user, which means that standard users do not have sufficient access to install programs. Windows Vista heuristically detects installation programs and requests administrator credentials or approval from the administrator user in order to run with access privileges. Windows Vista also heuristically detects updater and uninstallation programs. Note that a design goal of UAC is to prevent installations from being executed without the user's knowledge and consent since they write to protected areas of the file system and registry. Installer Detection only applies to: 32 bit executables Applications without a requestedExecutionLevel Interactive processes running as a Standard User with LUA enabled Before a 32 bit process is created, the following attributes are checked to determine whether it is an installer: Filename includes keywords like "install," "setup," "update," etc. Keywords in the following Versioning Resource fields: Vendor, Company Name, Product Name, File Description, Original Filename, Internal Name, and Export Name. Keywords in the side-by-side manifest embedded in the executable. Keywords in specific StringTable entries linked in the executable. Key attributes in the RC data linked in the executable. Targeted sequences of bytes within the executable.

You think that's bad, should see the net here in Aus. We haven't even got the cans yet, just the string. lol

Hi, thanks for the reply I have other priorities at work at the moment, so i have no time to test it right away. But once i've tested it, i'll post my findings here.

ok thanks, i reposted this question in the vista forum.

thanks for the quick reply. But signing the assembly (for both projects) doesn't seem to solve the problem. the same error occures. I tried adding test certificates to both projects, now i get an error that the manifest file can not be found... ps: i'm using visual studio 2005

Glad it worked. I just noticed that you're defining dbcc_name in C# to be short, even though it's char in C++. This probably means that you may access memory that you shouldn't, and might cause you an access violation. I think the most accurate representation in C# would be sbyte. My LinkedIn Profile

tnx for your reply this is not the actual code from the program, but it is however the actual code from a testprogram i wrote to simulate the problem. I commented out those lines so i did not have to print out a document every time i wanted to simulate the problem so running the code above will result in excel not being able to print...