You can also take a look at this here.




_________________________
-Vijay G
Strive for Perfection

For whatever reason the space appears to be removed automatically. But, things are working ok again for the user logging in.
I used Flush Privleges again. I deleted the user. Added the user again and defined the host as localhost, set a password and it worked; however, if I use the wildcard character % for the host name, the user still could not log in.

Two of the accounts have a username of monty and a password of some_pass. Both accounts are superuser accounts with full privileges to do anything. One account ('monty'@'localhost') can be used only when connecting from the local host. The other ('monty'@'%') can be used to connect from any other host. Note that it is necessary to have both accounts for monty to be able to connect from anywhere as monty. Without the localhost account, the anonymous-user account for localhost that is created by mysql_install_db would take precedence when monty connects from the local host. As a result, monty would be treated as an anonymous user. The reason for this is that the anonymous-user account has a more specific Host column value than the 'monty'@'%' account and thus comes earlier in the user table sort order. (user table sorting is discussed in section 5.4.5 Access Control, Stage 1: Connection Verification.)

That should explain your doubt on '%' thing.

Cheers!

_________________________
-Vijay G
Strive for Perfection

That explains it. Thank you.