View Single Post
  #29 (permalink)  
Old March 23rd, 2006, 08:57 PM
mimoss mimoss is offline
Registered User
 
Join Date: Mar 2006
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I too was getting the same message, concidentally on a Dell. My fix was easier than what is posted here, so if the cause of your message is the same as mine, you may find this works.

My problem was occuring whenever the user of my VB.NET 2003 application would attempt to launch his program from his desktop shortcut. If he attempted to execute the exe directly it worked fine. Why? I have no idea, I checked the shortcut and it was fine, besides I dont think the user would even know how to edit the shortcut. I deleted the existing shortcut and created a new one and the problem went away.

I wish I knew why this helped, but I have no clue.

Reply With Quote