Using VB6 application with Win32 API calls on Win 7 64-bit system

I am having difficulites installing and running custom VB6 applications on win7 64-bit system.
The application was built and deployed using package and deployment wizard.  It uses win 32 API calls to read an initialization file and logon to an odbc database.  The installation appears to go correctly but when running the application it does not seem to read the initialization file and errors ensue.

What am I missing in this scenario
lambautoAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

eemitCommented:
Where is the location of the ini file?

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
lambautoAuthor Commented:
The ini file is in the program files(x86)/appname/appname.exe  directory.
eemitCommented:
Hi lambauto,
according to microsoft:
"Applications should be installed to the Program Files folder by default.
User data or application data must never be stored in this location because
of the security permissions."

The best place to store application configuration data is AppData folder (CSIDL_APPDATA...).
Create subfolders below them for your data.
You'd first create a folder with your company name, then a subfolder below that
with the product name. You can create a further subfolder for each subsequent version.
Put your ini file in that folder.
lambautoAuthor Commented:
Thank you for your help.  This is a really old application and the ini file was in the path deemed appropriate at the time it was written.  You were correct in that the ini file could not be written to by the kernel because of the new security.  I placed the application in a different location and everything went fine.

Thanks for getting me to think about the ini file it was the key.
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
Microsoft Legacy OS

From novice to tech pro — start learning today.