Microsoft Visual C++ .NET Professional Projects - Premier Press

202 Project 1 DATABASE PROGRAMMING USING VC++.NET

FIGURE 8-28 The design of the Deposit/Withdrawal form

Table 8-5 Properties to be Set for the Deposit/Withdrawal Form

As in the previous form, you need not change the IDs of the static controls. However, you need to edit the IDs of the remaining edit, buttons, and combo box controls. Table 8-6 lists the controls and the value to be assigned to the ID property.

Table 8-6 IDs of Controls of the Deposit/Withdrawal Form

The next form to be designed is the Transfer Operations form.

Designing the Transfer Operations Form

In the same way as you handled the Login and the Deposit/Withdrawal forms, you need to add a class to handle the Transfer Operations form. Follow the same steps that you performed to add classes in the previous two sections. Specify the name of the class as CTransfer and the base class as CDialog. Correspondingly, two files, Transfer.h and Transfer.cpp, and a dialog resource are added to the project.

Next, to design the Transfer Operations form, perform the following steps:

1.Switch to the Resource View.

2.Select the dialog resource with the ID IDD_TRANSFER. This is the resource added by the wizard for the class that you just added.

3.Refer to Figure 8-29 to design the Transfer form.

Next, you need to set the properties of the form and the controls. Table 8-7 lists the properties to be set for the Transfer Operations form, IDD_DEPWDRL:

Table 8-7 Properties to be Set for the Transfer Operations Form

204 Project 1 DATABASE PROGRAMMING USING VC++.NET

FIGURE 8-29 The design of the Transfer Operations form

As in the previous form, you need not change the IDs of the static controls. For the remaining edit controls and buttons, you need to edit the IDs. Table 8-8 lists the controls and the value to be assigned to the ID property.

Table 8-8 IDs of Controls of the Transfer Operations Form

Editing the Application’s Menu

You are now ready with all form designs required for your application. Before you start to code the application, you need to edit the application’s main menu. By default, the wizard creates the menu that is shown in Figure 8-30.

FIGURE 8-30 The application’s original main menu

You need to edit the menu to reflect only the options required in your application. Following is the list of changes that you need to make to arrive at the design shown in Figure 8-5:

Remove the Edit menu option.

Remove the View menu option.

Remove the Print, Print Preview, and Print Setup options.

Insert an option Reports in the menu and the suboptions shown in Figure 8-31.

FIGURE 8-31 The Reports menu option

Coding the Application

With the designing in place, your next action is to code the application. I will explain the coding to be done to handle the following:

Logging process

Adding and editing records

Deactivate and reactivate records

Deposit/Withdrawal process

Transfer process

Issue check book process

// Remember to declare the variable, bCancelPressed, in the BankOpeartion.h //file. Declare it as a BOOL variable.

if (bCancelPressed)

//the bCancelPressed variable gets its value from the CloginDlg class. This value for this variable is set when the user presses either Cancel or Submit.

return FALSE;

// Remember to declare the variable, bLoginCorrect, in the BankOpeartion.h //file. Declare it as a BOOL variable.

if (!bLoginCorrect)

//bLoginCorrect also gets its value in the CloginDlg class where the login name //and password are accepted.

{

// Incorrect Login or Password AfxMessageBox(“Incorrect Login or Password.”);

if (i==2)

{

AfxMessageBox(“You have made 3 attempts.

Please contact admin for help. Can’t proceed.”); return FALSE;

}

}

else

{

break;

}

208 Project 1 DATABASE PROGRAMMING USING VC++.NET

}

else

{

return FALSE;

}

}

AfxEnableControlContainer();

//Standard initialization

//If you are not using these features and wish to reduce the size

//of your final executable, you should remove from the following

//the specific initialization routines you do not need.

//Change the registry key under which our settings are stored.

//TODO: You should modify this string to be something appropriate

//such as the name of your company or organization. SetRegistryKey(_T(“Local AppWizard-Generated Applications”));

LoadStdProfileSettings(); // Load standard INI file options (including MRU)

//Register the application’s document templates. Document templates

//serve as the connection between documents, frame windows and views.

CSingleDocTemplate* pDocTemplate;

pDocTemplate = new CSingleDocTemplate(IDR_MAINFRAME,

RUNTIME_CLASS(CBankOperationView));

AddDocTemplate(pDocTemplate);

// Parse command line for standard shell commands, DDE, file open CCommandLineInfo cmdInfo;

ParseCommandLine(cmdInfo);

//Dispatch commands specified on the command line if (!ProcessShellCommand(cmdInfo))

return FALSE;

//The one and only window has been initialized, so show and update it.

m_pMainWnd->SetWindowPos(&CWnd::wndTop, 0, 0, 660, 440, SWP_DRAWFRAME);

m_pMainWnd->CenterWindow(); m_pMainWnd->ShowWindow(SW_SHOW); m_pMainWnd->UpdateWindow();

return TRUE;

}

The explanation for the preceding code snippet follows:

When you execute your application, the control passes onto the InitInstance function. Therefore, in this function, you need to add the code to display the Login form and, hence, declare a pointer to the CLoginDlg class.

Only three attempts to log in are allowed; hence, you need to add a loop that will run exactly three times.

Within the loop, the control passes on to the dialog box class that will handle the login validation part. (You will next learn to code the validation. The dialog box class will validate and return a success or failure status back to this function.)

If the status as returned by the dialog class is successful, then you need to exit from the loop. Then the control passes to the line following the end of the while loop. Then the document template is created and the main view of the application, CBankOperationView, that is associated with the Account_Detail form is loaded.

If the status returned indicates failure, then check whether three attempts are over. If all three attempts are not successful, then break out of the loop and end the application.

The next task is to retrieve the value that the user enters and validate it against the values stored in the BankLogin table. To validate the user input with the values