Q:

VFP Entity Framework Provider getting encrypted password as empty string

I am using VFP Entity Framework Provider for .NET (EF) to read data from a VFP database. 
In the user table there is a password column.  When I get focus in the password cell in VFP I can easily copy the value and edit it:

On the .NET side the value is read without any problems. 
Now once in a while there is a peculiar row with a password with trailing spaces:

When I put focus in that cell VFP acts like there's no value at all:

When I retrieve that user in my program using Entity Framework I get an empty string.  I don't know how this password is generated, all I know is that it works for the original VFP program using the database.  There is no problem with other passwords, and this happens rather rarely, but repetitively. 
What is the source of that behavior?  Is there a workaround to retrieve the correct value on the .NET or VFP side? 

A:

I contacted Tom Brothers, the creator of VFP provider for EF simultaneously to posting this question.  He took his time and actually came up with the following diagnosis: 

The problem is that the invalid password’s first character is actually a null (ascii 0).   Typically, a null character is used as a string terminator.   Given this scenario .Net is returning an empty string because it didn’t find any characters before the null.   You can verify things are working the way I described them by inserting a null in the middle of one of your working passwords to see that it (“it” being .Net or the browse window) doesn’t return any characters after the null.   But the real annoying thing in your case is that VFP doesn’t seem to use the null as a terminator when accessing the table field directly… which is inconsistent with how the browse windows works when you click on the cell to edit the value. 

This is not a solution for the problem but constitutes the most completed answer.  Thank you Tom! 