🚀 go-pugleaf

"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote
> I have the following code, which create an INI file variable, and read a 
> section out of the INI file. edAttach and edPicsPath are TEdit controls.
>      S:=TStringList.Create;
>      FName:=ExtractFilePath(ParamStr(0))+'file.ini';
>      IniF:=TIniFile.Create(FName);
>      IniF.ReadSection('FILLERSETS',S);
>      edAttach.Text:=S.Values['Attachments'];
>      edPicsPath.Text:=S.Values['Images'];
> When debugging, the FName is set properly to the correct full file path. 
> But when reading the section and its values, its always empty.
> ... 
> Somehow, IniF is not created properly.

Monzer,

Have you updated, closed, or freed the INI file and 
tried looking at it with NotePad?

Rgds, JohnH

John Herbster wrote:
> "Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote
>> I have the following code, which create an INI file variable, and read a 
>> section out of the INI file. edAttach and edPicsPath are TEdit controls.
>>      S:=TStringList.Create;
>>      FName:=ExtractFilePath(ParamStr(0))+'file.ini';
>>      IniF:=TIniFile.Create(FName);
>>      IniF.ReadSection('FILLERSETS',S);
>>      edAttach.Text:=S.Values['Attachments'];
>>      edPicsPath.Text:=S.Values['Images'];
>> When debugging, the FName is set properly to the correct full file path. 
>> But when reading the section and its values, its always empty.
>> ... 
>> Somehow, IniF is not created properly.
> 
> Monzer,
> 
> Have you updated, closed, or freed the INI file and 
> tried looking at it with NotePad?
> 
> Rgds, JohnH

Hi John,
Yes, I tried all possible cases. This is really strange.

Regards

"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote

>>> I am using Delphi 2007 for Win32 / Vista Business Edition
>>> ... Somehow, IniF is not created properly.

>> Have you updated, closed, or freed the INI file and 
>> tried looking at it with NotePad?

> Yes, I tried all possible cases.

Monzer,

So what did NotePad show you?  
Did it look like a properly constructed INI file?

In order to avoid spelling mistakes I usually parameterize the 
names --  maybe something like this:: 

Const {To be used for both reading and writing}
  IniFileName    = 'File.INI';
    FillerSectName = 'FILLERSETS';
      AttachmentsName = 'Attachments';
      ImagesName      = 'Images';

procedure TForm1.Button1Click(Sender: TObject);
var SL: TStringList; IniF: TIniFile; FName, s: string;
begin
  FName:=ExtractFilePath(ParamStr(0)) + IniFileName;
  IniF:=TIniFile.Create(FName);
  Try
    SL := TStringList.Create;
    IniF.ReadSection(FillerSectName,SL);
    edAttach.Text   := SL.Values[AttachmentsName];
    edPicsPath.Text := SL.Values[ImagesName];
  Finally
    SL.Free;
    IniF.Free;
  End;
end;

I see that you are using Vista.  
Does your EXE directory permit writing of an INI file?

Rgds, JohnH

hi
Thanks for your support. I found the problem. For a reason, the
application was looking for the file in the Windows\System directory
rather than looking into the same folder of the EXE. This is funny.
When I included he file path, then it works fine.

Regards

On Sat, 28 Jun 2008 20:17:51 -0500, "John Herbster"
<herb-sci1_AT_sbcglobal.net> wrote:

>"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote
>
>>>> I am using Delphi 2007 for Win32 / Vista Business Edition
>>>> ... Somehow, IniF is not created properly.
>
>>> Have you updated, closed, or freed the INI file and 
>>> tried looking at it with NotePad?
>
>> Yes, I tried all possible cases.
>
>Monzer,
>
>So what did NotePad show you?  
>Did it look like a properly constructed INI file?
>
>In order to avoid spelling mistakes I usually parameterize the 
>names --  maybe something like this:: 
>
>Const {To be used for both reading and writing}
>  IniFileName    = 'File.INI';
>    FillerSectName = 'FILLERSETS';
>      AttachmentsName = 'Attachments';
>      ImagesName      = 'Images';
>
>procedure TForm1.Button1Click(Sender: TObject);
>var SL: TStringList; IniF: TIniFile; FName, s: string;
>begin
>  FName:=ExtractFilePath(ParamStr(0)) + IniFileName;
>  IniF:=TIniFile.Create(FName);
>  Try
>    SL := TStringList.Create;
>    IniF.ReadSection(FillerSectName,SL);
>    edAttach.Text   := SL.Values[AttachmentsName];
>    edPicsPath.Text := SL.Values[ImagesName];
>  Finally
>    SL.Free;
>    IniF.Free;
>  End;
>end;
>
>I see that you are using Vista.  
>Does your EXE directory permit writing of an INI file?
>
>Rgds, JohnH

"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote
> ... the application was looking for the file in the Windows\System
> directory rather than looking into the same folder of the EXE. ...
> When I included he file path, then it works fine.

Monzer,

Please be aware that the folder where the EXE resides may 
become readonly in future versions of Windows.

Regards, JohnH

"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote in message 
news:j7em7455nufa9o13dn8vhi6eo76s0gbbjt@4ax.com...

> Thanks for your support. I found the problem. For a reason,
> the application was looking for the file in the Windows\System
> directory rather than looking into the same folder of the EXE.

That is what it is supposed to do when you don't specify a full path, just a 
filename.


Gambit 

Hi
Logically, it should look first in the current directory of the EXE
before going to Windows\System folder. 

anyway, thanks for your kind support.

On Mon, 14 Jul 2008 10:39:49 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote:

>
>"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote in message 
>news:j7em7455nufa9o13dn8vhi6eo76s0gbbjt@4ax.com...
>
>> Thanks for your support. I found the problem. For a reason,
>> the application was looking for the file in the Windows\System
>> directory rather than looking into the same folder of the EXE.
>
>That is what it is supposed to do when you don't specify a full path, just a 
>filename.
>
>
>Gambit 
>

> Logically, it should look first in the current directory of the EXE
> before going to Windows\System folder. 

You are confusing the 'current directory' (set explicitly with
SetCurrentDir and implicitly through a file dialog, amongst other
possible things) with the directory in which the EXE resides.

"Monzer George Yazigi" <monzer_yazigi@hotmail.com> wrote in message 
news:ur8n74l1t5ct0qd6oj0jiop1hcr8t3lbkr@4ax.com...

> Logically, it should look first in the current directory of
> the EXE before going to Windows\System folder.

Windows INI files are not that logical, though.  In the Windows 3.1 days, 
all INI files were stored underneath the system folder, and no file paths 
were specified in code when accessing them.  So, for backwards 
compatibility, Win9x onwards have to maintain that logic when no paths are 
specified for INI files.  If you want to access an INI file in a specific 
location, you have to provide the full path.


Gambit