.Net (2005) MDI Application runs fine in Windows XP and Vista but fails on startup in Windows 7 64-bit

I am getting my lips beat off.  I have an application that is a VB.Net (2005) MDI application.  It is developed on Windows XP (SP2) and tested on Windows XP (SP2) and Vista (SP1)....runs great with no problems.  The folks I wrote it for installed it on a new laptop running Windows 7 64 Bit Home Premium.  The application starts, shows the spash screen and then crashes with the error message "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is avaliable", then the only option is to click on Close Program (error message screen capture is attached).  I went in and set the compatibility mode for the application EXE on the Windows 7 laptop to run in Windows XP (SP2) and granted administrator rights to the application and it still fails (screen capture of these settings attached).  This is driving me nuts.  It's the first time I've attempted to run a 32 bit developed application on a 64 bit machine and I'm sure that I'm missing something simply but all of the research that I've done over the last 2 days has not helped one bit.


WMCErrorMessage.bmp
WMCCompatibilitySettings.bmp
rlaws69Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

ChloesDadCommented:
Does the program install into the "program files" folder, and if so does it write to files there. We have a similar problem with our software on Windows 7 and the only solution was to install it outside of "program files"
0
rlaws69Author Commented:
It is installed in the C:\Program Files(86)\xxxxx.  So you installed it outside the Program Files directory and it worked?  I will try that now.
0
rlaws69Author Commented:
That didn't work either.  I get the same error message.
0
Cloud Class® Course: CompTIA Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

grayeCommented:
Well, one of the things you can do is recompile the project as a 32-bit only application.   Recall, that by default, VS2005 uses the Target CPU setting of "AnyCPU"... which means that it will magically convert to a 64-bit application when run on a 64-bit OS.   But, if you change the setting to "x86", then it will remain as a 32-bit applicaiton when run on either a 32 or 64-bit OS.
http://msdn.microsoft.com/en-us/library/07bysfz2.aspx
Note that although this will probably fix the problem, but you might wanna go back later and find/fix the real problem.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
rlaws69Author Commented:
I'm going to see about giving that a shot today.  I really appreciate the help.
0
rlaws69Author Commented:
Graye thanks so much for the help!!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.