I don't believe this is possible, at least not without using an external non-SQL table.
The problem is if the login failed you don't have access to the SQL tables to make a record of it.
This recording has to be handled by the SQL Server itself and the application is not logged in. So you would need SQL Server 2005 and v9.0 of Great Plains and Windows Server 2003 with Active Directory.
I looked into this when I developed Winthrop's (now Rockton's) Omni Password product.
David Musgrave [MSFT]
Senior Development Consultant
Escalation Engineer - Great Plains
Microsoft Dynamics Support - Asia Pacific
Micorosoft Dynamics (formerly Microsoft Business Solutions)
Any views contained within are my personal views and
not necessarily Microsoft Business Solutions policy.
This posting is provided "AS IS" with no warranties,
and confers no rights.