Solved

.ini file

Posted on 2000-03-19
1
256 Views
Last Modified: 2010-04-04
In my application, there are two report forms. when closing each report form, the report form write the left, top, height, width into .Ini file, so next time the report will show on position as  that on last time.
When I click a button and produce a report A and close it, then click another button to generate another report B, and close it, thare are no problem.
When I produce report A and than report B, then close A( or B), it is still fine, but when I then close B(or A), I got the TExternalException message.
I find when write the form.left into the .ini file, the error message occurs.

The following is the procedure that write the .ini file

procedure WriteIni(formname : TForm);
var status : integer;
    Ininame: string;
begin
  Status := 1;
  if not assigned(SptIni) then
  begin
    Ininame := ExtractFilePath(ParamStr(0)) + 'fSptIni.ini';
    SptIni := TIniFile.Create(Ininame);
  end;

  with SptIni do begin
    case formname.WindowState of
      wsNormal: begin
          WriteInteger('Support', 'Left', formname.Left);
          WriteInteger('Support', 'Top', formname.Top);
          WriteInteger('Support', 'Width', formname.Width);
          WriteInteger('Support', 'Height', formname.Height);
        end;
      wsMiniMized:
          Status := 2;
      wsMaximized:
          Status := 3;
    end;//case
  if not formname.Active then
    Status := 2;
    {write status information}
  SptIni.WriteInteger ('Support', 'Status', Status);
  {destroy the IniFile object}
  SptIni.Destroy;
  end;
end;


Best regards

PeterShaw
 
0
Comment
Question by:petershaw9
1 Comment
 
LVL 12

Accepted Solution

by:
rwilson032697 earned 50 total points
ID: 2634242
Try writing the procedure like this, with the INI file obkect locally:

procedure WriteIni(formname : TForm);
var status : integer;
    Ininame: string;
    SptIni : TIniFile;
begin
  Status := 1;
  Ininame := ExtractFilePath(ParamStr(0)) + 'fSptIni.ini';
  SptIni := TIniFile.Create(Ininame);

  with SptIni do begin
    case formname.WindowState of
      wsNormal: begin
          WriteInteger('Support', 'Left', formname.Left);
          WriteInteger('Support', 'Top', formname.Top);
          WriteInteger('Support', 'Width', formname.Width);
          WriteInteger('Support', 'Height', formname.Height);
        end;
      wsMiniMized:
          Status := 2;
      wsMaximized:
          Status := 3;
    end;//case
  if not formname.Active then
    Status := 2;
    {write status information}
  SptIni.WriteInteger ('Support', 'Status', Status);
  {destroy the IniFile object}
  SptIni.Free;
  end;
end;

Cheers,

Raymond.

0

Featured Post

3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Introduction Raise your hands if you were as upset with FireMonkey as I was when I discovered that there was no TListview.  I use TListView in almost all of my applications I've written, and I was not going to compromise by resorting to TStringGrid…
In my programming career I have only very rarely run into situations where operator overloading would be of any use in my work.  Normally those situations involved math with either overly large numbers (hundreds of thousands of digits or accuracy re…
In a recent question (https://www.experts-exchange.com/questions/28997919/Pagination-in-Adobe-Acrobat.html) here at Experts Exchange, a member asked how to add page numbers to a PDF file using Adobe Acrobat XI Pro. This short video Micro Tutorial sh…

777 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question