S
SteveW
I develop and maintain several software tools (MS Office Type) in my company
for members of the department to use.
Most of these tools are VBA (MS Excel & WRQ Reflections mostly) driven and
require a "centralized" initialization file that provides various
information for the application to use.
By centralized, I mean that the application (and its INI file) will be
stored on a shared network drive and can be started by anybody in the
department. This also does not prevent people from copying the application
to their local computer to run. The way the program is written insures that
the initialization information always comes from the network drive "INI"
file.
One of the requirements I have is to provide a "version control" to insure
that anybody that has an older version of the application cannot start it
and possibly cause damage to the resulting information.
I have been accomplishing this by using the Win32 APIs
GetPrivateProfileString and WritePrivateProfileString functions. Every time
I explore these APIs on the Microsoft site, it has a warning, and I quote
"Note This function is provided only for compatibility with 16-bit
Windows-based applications. Applications should store initialization
information in the registry."
These applications must have a centralized initialization primarily because
there is data stored in the "INI" file that gets updated (to include the
versioning entry "CurrentVersion") which is used by the application.
My question is this: Is it possible to set up a "remote" registry file that
can be used in this manner for initialization of my application so that
anybody in the department can use the application and have access to the
same information?
Thanks,
for members of the department to use.
Most of these tools are VBA (MS Excel & WRQ Reflections mostly) driven and
require a "centralized" initialization file that provides various
information for the application to use.
By centralized, I mean that the application (and its INI file) will be
stored on a shared network drive and can be started by anybody in the
department. This also does not prevent people from copying the application
to their local computer to run. The way the program is written insures that
the initialization information always comes from the network drive "INI"
file.
One of the requirements I have is to provide a "version control" to insure
that anybody that has an older version of the application cannot start it
and possibly cause damage to the resulting information.
I have been accomplishing this by using the Win32 APIs
GetPrivateProfileString and WritePrivateProfileString functions. Every time
I explore these APIs on the Microsoft site, it has a warning, and I quote
"Note This function is provided only for compatibility with 16-bit
Windows-based applications. Applications should store initialization
information in the registry."
These applications must have a centralized initialization primarily because
there is data stored in the "INI" file that gets updated (to include the
versioning entry "CurrentVersion") which is used by the application.
My question is this: Is it possible to set up a "remote" registry file that
can be used in this manner for initialization of my application so that
anybody in the department can use the application and have access to the
same information?
Thanks,