Frustrating problem. I have a .dll [created in VB6] that is called by all
the .NET programs that we are developing.
The dll reads an .ini file to determine if it should fill a data dictionary
from the development or production SQL Server. If no .ini is found it
defaults to production.
I recently started using a new PC with Win XP. The process works except for
finding the .ini file. I always get the production environment as if the
..ini does not exist. Other developers have upgraded to Win XP and do not
have this problem.
Are there any suggestions? I have reregistered the dll; moved the .ini file
to the C:\ root and to the startup directory of the program I'm developing;
and attempted to step thru the code. I am unable to determine why the dll
does not find the ini file.
Bob