English Deutsch Français Italiano Español Português 繁體中文 Bahasa Indonesia Tiếng Việt ภาษาไทย
All categories

2 answers

Create a good schema in the database. I would go for following tables (With columns in brackets) assuming you are talking about loan recoveries:
Customers (Cust_Id, First Name, Last name, Birth Date, Contact number, address etc)
products (product_id, name, total_cost, etc.) -> stores loan details
Cust_loan(cust_id, product_id, down_pymt, paymt_method (like cheque, draft, auto debit etc), installment_amount, no. of installments)
installments (cust_id, product_id, inst date, inst amt).

Create forms for: adding/querying customers/products i.e loans and installments.
Generate reports for installment defaulters and use that for recovery.

HTH.

2006-08-03 21:56:10 · answer #1 · answered by Indian_Male 4 · 0 0

Such a program could never be complete for a VB program because it would rely on most of the same files as those needed by the program being repaired!

A recovery program would simply keep copies of the installed data files, and let the user specify which to restore. If you want to get fancy, you could search in the registry to find out where the program is installed. Then you'd do ChDir App.Path and for each file use the FileCopy statement. You could also write a checksum by reading the files in binary mode and saving a text file containing the sum. Then do the same check on the installed files to see if they are broken.

2006-08-04 03:52:05 · answer #2 · answered by jacinablackbox 4 · 0 0

fedest.com, questions and answers