I have created a login form which holds buttons corresponding to users' names held in an Access file. The buttons are created in the OnCreate event because I don't want to have to create them each time the screen is shown.
The buttons display as expected, and I have created LogOn and LogOff procedures, which both work as I expected.
The next step was to only display the buttons for users who are currently logged on to the system. To do this, I have created the following code in the OnActivate event:
procedure TUserInForm.FormActivate(Sender: TObject);
var
btn : TLBButton;
begin
With UserQuery do begin;
first;
while (not eof) do begin
BtnName := FieldByName('UserName').AsString;
Btn := TLBButton(FindComponent(BtnName));
if (Btn <> nil) then
if (FieldByName('LoggedIn').AsBoolean = True) then Btn.Visible := True else Btn.Visible := False;
next;
end;
end;
end;
However, it doesn't find any of the buttons - they are all nil. The code throws an Access Violation exception if I remove the nil check. But, at no point in the code do I destroy the buttons or the form itself. The buttons exist, because I can see them on the form. The BtnName variable is global within the unit. I've checked that the BtnName variable is populated correctly from the table.
I've used code similar to this to find components before, with no problems. In fact, I "stole" the code shown above from another procedure (with the obvious changes) in which it works fine. The logs show no errors.
Can anyone suggest some approach to fixing this problem? It's very frustrating!
FindComponent()searches the owned-components-list of the component that it is called on. I’m assuming yourOnCreatehandler creates the buttons with the Form as theirOwner. But thewithblock will causeFindComponent()to be called on theUserQuerycomponent instead of the Form. That would explain why the buttons are not being found.So, you can either:
Self.FindComponent()instead, since theOnActivatehandler is being called on the Form, soSelfwill point at the Form:withblock altogether, as it is generally considered to be bad practice to usewithanyway in non-trivial cases (this situation is a good example of why):withblock, you can move the button search to a separate function that does not exist in theUserQuerycomponent, so thewithwon’t be confused about which component to call the function on:Now, that being said, it would be a better design to add the created buttons to a list that you manage for yourself, rather than a list that the VCL manages on your behalf. Then you will always know exactly where to find the buttons. For example: