In the past I've used ini type files extensively for storing data that
I want access from multiple workbooks. For example, in my current
project I want to store cost coefficients for various types of
equipment:

[Compressor]
a = 1
b = 1.34
c = 10.2

[Pump]
a = 2
b = 1.5
c = 9.0

The _PrivateProfileString API functions have been easy to use (and
don't require a lot of code) for reading and writing to the ini file.
But there is always the risk that they will no longer be supported
and, if nothing else, are considered out-dated. So what is the new
alternative? I've had a quick look for information on xml but haven't
found anything I could understand - it seems to be solving a much
bigger problem than the one I have here - but maybe I'm just not onto
the right link.

Appreciate any thoughts/ recommendations.

Thanks a lot,
Andrew

Nothing wrong with .ini files that I can see and I am sure those API
functions will remain
for a very long time to come. Unless you have other reasons to change I
would stick to .ini files.

RBS


"Andrew" wrote in message
...
In the past I've used ini type files extensively for storing data that
I want access from multiple workbooks. For example, in my current
project I want to store cost coefficients for various types of
equipment:

[Compressor]
a = 1
b = 1.34
c = 10.2

[Pump]
a = 2
b = 1.5
c = 9.0

The _PrivateProfileString API functions have been easy to use (and
don't require a lot of code) for reading and writing to the ini file.
But there is always the risk that they will no longer be supported
and, if nothing else, are considered out-dated. So what is the new
alternative? I've had a quick look for information on xml but haven't
found anything I could understand - it seems to be solving a much
bigger problem than the one I have here - but maybe I'm just not onto
the right link.

Appreciate any thoughts/ recommendations.

Thanks a lot,
Andrew

Thanks for your thoughts. It seems it must be about 8 or more years
ago that I first saw someone state that these API functions would be
around for a long time ... you don't think that time may be coming
around? From a learning point of view I had hoped that if ini files
were to be deprecated that they would be replaced with something newer
and even better. Have you played around with xml - is it as bad as
what it seems? I guess some sort of basic database would be a more
"professional" way to go about it but presumably running queries
wouldn't be so straight foward unless support was built into VBA. No
other real reasons to move away from ini files though.

Thanks again,
Andrew



On 31 Aug, 16:50, "RB Smissaert"
wrote:
Nothing wrong with .ini files that I can see and I am sure those API
functions will remain
for a very long time to come. Unless you have other reasons to change I
would stick to .ini files.

RBS

"Andrew" wrote in message

...



In the past I've used ini type files extensively for storing data that
I want access from multiple workbooks. *For example, in my current
project I want to store cost coefficients for various types of
equipment:

[Compressor]
a = 1
b = 1.34
c = 10.2

[Pump]
a = 2
b = 1.5
c = 9.0

The _PrivateProfileString API functions have been easy to use (and
don't require a lot of code) for reading and writing to the ini file.
But there is always the risk that they will no longer be supported
and, if nothing else, are considered out-dated. *So what is the new
alternative? *I've had a quick look for information on xml but haven't
found anything I could understand - it seems to be solving a much
bigger problem than the one I have here - but maybe I'm just not onto
the right link.

Appreciate any thoughts/ recommendations.

Thanks a lot,
Andrew- Hide quoted text -

- Show quoted text -

you don't think that time may be coming around?

No, not at all.
As you say, no real reason to move away from .ini files, so I would stick
with it.

RBS


"Andrew" wrote in message
...
Thanks for your thoughts. It seems it must be about 8 or more years
ago that I first saw someone state that these API functions would be
around for a long time ... you don't think that time may be coming
around? From a learning point of view I had hoped that if ini files
were to be deprecated that they would be replaced with something newer
and even better. Have you played around with xml - is it as bad as
what it seems? I guess some sort of basic database would be a more
"professional" way to go about it but presumably running queries
wouldn't be so straight foward unless support was built into VBA. No
other real reasons to move away from ini files though.

Thanks again,
Andrew



On 31 Aug, 16:50, "RB Smissaert"
wrote:
Nothing wrong with .ini files that I can see and I am sure those API
functions will remain
for a very long time to come. Unless you have other reasons to change I
would stick to .ini files.

RBS

"Andrew" wrote in message

...



In the past I've used ini type files extensively for storing data that
I want access from multiple workbooks. For example, in my current
project I want to store cost coefficients for various types of
equipment:

[Compressor]
a = 1
b = 1.34
c = 10.2

[Pump]
a = 2
b = 1.5
c = 9.0

The _PrivateProfileString API functions have been easy to use (and
don't require a lot of code) for reading and writing to the ini file.
But there is always the risk that they will no longer be supported
and, if nothing else, are considered out-dated. So what is the new
alternative? I've had a quick look for information on xml but haven't
found anything I could understand - it seems to be solving a much
bigger problem than the one I have here - but maybe I'm just not onto
the right link.

Appreciate any thoughts/ recommendations.

Thanks a lot,
Andrew- Hide quoted text -

- Show quoted text -