Hi Radharani,

This is a very simple sample code of login button:

STRING ls_username

STRING ls_password

INTEGER li_count

ls_username = TRIM(sle_username.Text)

ls_password = TRIM(sle_password.Text)

SELECT COUNT(*)

INTO :li_count

FROM USERS

WHERE USER_ID = :ls_username

AND PASSWORD = :ls_password

USING SQLCA;

IF li_count = 1 THEN

   Open(w_test)

ELSE

   MessageBox("Warning!", "The Username and/or password is invalid! Try again.")

END IF

Hi Radharani,

Here's a sample code for saving data to the database:

//************************************************************

// Variable Declarations

//************************************************************

STRING ls_username

STRING ls_password

INTEGER li_count

//We Initialize the variables by trimming blank spaces from the Single Line Edit Controls

ls_username = TRIM(sle_username.text)

ls_password = TRIM(sle_password.text)

//************************************************************

// Logic of the Script

//************************************************************

//Insert the values into the Database

INSERT INTO USERS (USER_ID, USERNAME, PASSWORD)

VALUES (123, :ls_username, :ls_password)

USING SQLCA;

//Check for any database errors

IF SQLCA.SQLCODE <> 0 THEN

   //If an error: notify the user

   MessageBox("Database Error!", "Error while saving data to the database. Error message: [" + STRING(SQLCA.SQLCODE) + "] - " + SQLCA.SQLERRTEXT)

ELSE

   //If everything OK, Notify the user

   MessageBox("Data saved!", "The data has been successfully saved to the database!")

END IF

Remember: It's always good practice to check if the data already exists before saving it.

Regards,

Hi Radha,

Are you sure you want to save the combination in the database?
From a security perspective you never want to save the password, not even the failed login passwords because saving it means that someone can read it later.

You may opt for embedded SQL (see previous answers to your question) or use a DataWindow object in a DataStore to save whatever login related data is needed in your particular case. I have sometimes seen the following data saved when a user logs on:

• UserID and LoginTimestamp - because you want to audit logins
• ApplicationID and Version - because you want to track what application logic is accessing your database

HTH /Michael