.INI versus Registry
 

Hi,

i have an application witch i saved on a netwerk drive as a template
in a folder named TEMPLATE.
The application contains a worksheet with the 'common' settings as
template location, printer names, ...
I have 2 PC's that i use to run this application.
When i read this forum there are 2 possibilities to store settings, in
a .INI file or save it in the REGISTRY (Getsetting / Savesetting).

I suppose that, when saving it into the registry that this is on the
local machine where the application (copy of the template) runs.
This means then that the 'common' setting need to be available on
every machine where this application runs, are am i wrong?

This is where i see the advantage of a .INI file versus the registry
because this can be also on the network drive and common to all PC's
where the application runs.
the application runs.

I'm still on Win XP professional & Office 2003, but don't know for how
long.

So my question is: what would you recommand to use, a .INI file or the
Registry?

Regards,
Ludo

.INI versus Registry
 

Very very simplified: The registry follows the user profile. When I log on,
my own saved preferences are loaded. An ini file with a hardcoded path will
load last saved no matter who saved it.

So this depends on what you're about to do. "Last used invoice number"
definitely in an ini file type of thing, "preferred color theme" definitely
in the registry.

HTH. Best wishes Harald



"Ludo" wrote in message
...
Hi,

i have an application witch i saved on a netwerk drive as a template
in a folder named TEMPLATE.
The application contains a worksheet with the 'common' settings as
template location, printer names, ...
I have 2 PC's that i use to run this application.
When i read this forum there are 2 possibilities to store settings, in
a .INI file or save it in the REGISTRY (Getsetting / Savesetting).

I suppose that, when saving it into the registry that this is on the
local machine where the application (copy of the template) runs.
This means then that the 'common' setting need to be available on
every machine where this application runs, are am i wrong?

This is where i see the advantage of a .INI file versus the registry
because this can be also on the network drive and common to all PC's
where the application runs.
the application runs.

I'm still on Win XP professional & Office 2003, but don't know for how
long.

So my question is: what would you recommand to use, a .INI file or the
Registry?

Regards,
Ludo

.INI versus Registry
 

On 31 aug, 16:16, "Harald Staff" wrote:
Very very simplified: The registry follows the user profile. When I log on,
my own saved preferences are loaded. An ini file with a hardcoded path will
load last saved no matter who saved it.

So this depends on what you're about to do. "Last used invoice number"
definitely in an ini file type of thing, "preferred color theme" definitely
in the registry.

HTH. Best wishes Harald

"Ludo" wrote in message

...



Hi,

i have an application witch i saved on a netwerk drive as a template
in a folder named TEMPLATE.
The application contains a worksheet with the 'common' settings as
template location, printer names, ...
I have 2 PC's that i use to run this application.
When i read this forum there are 2 possibilities to store settings, in
a .INI file or save it in the REGISTRY (Getsetting / Savesetting).

I suppose that, when saving it into the registry that this is on the
local machine where the application (copy of the template) runs.
This means then that the 'common' setting need to be available on
every machine where this application runs, are am i wrong?

This is where i see the advantage of a .INI file versus the registry
because this can be also on the network drive and common to all PC's
where the application runs.
the application runs.

I'm still on Win XP professional & Office 2003, but don't know for how
long.

So my question is: what would you recommand to use, a .INI file or the
Registry?

Regards,
Ludo- Tekst uit oorspronkelijk bericht niet weergeven -

- Tekst uit oorspronkelijk bericht weergeven -

Thanks Harald for this explanation.
Ludo