Re: Access Bankng Solution

mazubair_at_gmail.com wrote:

>The expertise level of the user of the solution is very low. High end
>Database will not be suitable for them.

The expertise of the end-user may be low, but that doesn't mean that you (presumably the programmer) can't hide complex database functionality behind a relatively simple user interface.

>I intend to develop the solution with MS Access as Database,

I wouldn't touch Access with a ten foot pole for an application that has to store and manipulate important data (like how much money is in account X). You've got to think in terms of disaster recovery, replication and the like - Access simply isn't up to the job.

> Visual Basic as Tool and Crystal Report as Report Builder.

If you're a VB expert, then use VB - personally I would choose Delphi.

>Should I ?

>1) Proceed with the Idea.

Choose a decent database first. There are good free ones out there, Firebird (my choice), or you could use PosgreSQL. IBM, Oracle, MSoft, Sybase all produce database systems better than Access.

>2) For better performance should I split the Transactions Table for
>different types of Accounts. There will be maximum 200000 records in
>whole yearly.

200.000 records is nothing for a modern database system.

>3) Split the Cheque information Table (Account Type wise or Year wise)
>which will store 500000 yearly records.

Neither is 500.000

>4) Some one are suggesting using different databases for different
>types of account. Should I go for that.

No - I would not do this. A relational database system is designed around the notion of a transaction, which is a piece of processing that either succeeds totally or fails totally.

If there are relationships between the different types of account (say, the same person has 3 accounts), and you want to know, say for example, how much money this person has at a given time, you will have to query the database(s). Now, if you have 3 different databases, you can't be certain that at a point in time X, that all the transcations on the three different accounts are consistent, whereas within one RDBMS, you should have a consistent view of the data at all times.

>Your valued suggestion will help me a lot to take decision.

I'm asking myself why you don't purchase a solution off the shelf that is tried and tested with many customers already (ask for customer reference sites)?

What do these bank branches use at the moment to keep track of their customers' money?

Paul...

>M. A. Zubair
>mazubair_at_gmail.com

-- 

plinehan __at__ yahoo __dot__ __com__

XP Pro, SP 2, 

Oracle, 9.2.0.1.0 (Enterprise Ed.)
Interbase 6.0.2.0;

When asking database related questions, please give other posters 
some clues, like operating system, version of db being used and DDL.
The exact text and/or number of error messages is useful (!= "it didn't work!").
Thanks.
 
Furthermore, As a courtesy to those who spend 
time analyzing and attempting to help, please 
do not top post.