### User Login Screen

[irfanhabib]

Dear All Experts -

This is very informatic and real helping platform for all users , i feel day by day
my skills improved and i am very happy, i am part of this professional community.

My User Login Screen Coding Present In Usrlog.prg File. In passord input field
i use COLO N+,N , i use this only for when user input in password field ,no text
display and only cursor movement display.

My Requirements
================
if possible guide me , when user type password in password field, ( ***** ) display in password
field and cursor move farward.

I am very thankful, if provide solution code in prg file.

Very Best Regards
Irfan Habib

 

[JRB-Bldr]

By using the Search tools of this forum, I found:

http://www.tek-tips.com/viewthread.cfm?qid=1182847

You might want to look at it to find your answer.

Good Luck,
JRB-Bldr

 

[Olaf Doschke]

That should do it, besides you still expect legacy solutions in the VFP forum, please post this in forum182
Please consider this for future posts, don't be afraid you'll not be discovered there.

As you still consider this the forum to post and we're not the forum cops:
The VFP way would be setting the PasswordChar property of a textbox to "*" and the rest is automatic.

Obviously you have to go through much more code to make this work on an @say or @get. Therefore even though you say you don't know forms, it's a simple form to start with judged from the form structure itself, though Login is an advanced topic. You may consider learning to do forms now and create a simple login SCX form instead of screen PRG code. It only takes two textboxes for user and password and a commandbutton "Login".

And while it breaks the UI, it's just a simple popup window appearing at Login.

Bye, Olaf.

 

[Mike Lewis]

Re Mroth36's solution in the thread that JRB posted: It works fine, as far as it goes. But it has the disadvantage that the user can't backspace to correct a mistake, nor can he paste into it password (it would only paste one character at a time). You could code round those two issues - at the cost of greater complexity. It's another argument for using a form.

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads