stickleprojects Level: Moderator

 Registered: 09-09-2002 Posts: 891
|
Re: Database
Hi,
You have a couple of options:
1. Access database with no visual basic code
2. Access database with a visual basic application to read/update the database.
I would recommend that you create your database using Access only and then create a vb application afterwards. This will help you iron out your system design before embarking on a full vb app.
How much knowledge do you have?
What restrictions are there (ie. what computer will this run on, etc.)
How many users?
To start your design, write down in English as complete a description of what you want the system to do.
For example:
I want to write a system that allows the user to reserve hotel rooms and send out bills to clients. I don't know how many rooms are in the hotel, but some of them will be occupied and will not be able to be reserved. All reservations will be for 1 week or more.
Next, take all of the NOUNS from this statement. This will given you an idea of the structure of the information and how it will be used.
For example:
USER, HOTEL, HOTEL ROOM, BILL, CLIENT, RESERVATION
You can imply associations between these items (called Entities in design-speak) from your previous statement.
A HOTEL ROOM may be occupied by a CLIENT
A CLIENT may have one or more RESERVATIONs
A RESERVATION will be associated with a BILL
A CLIENT will receive a BILL
A HOTEL will have one or more HOTEL ROOMs
Your system will have to produce the BILLs, so you will probably need some sort of reports. Do you use Word, Excel, or Access Reports or what? It's up to you - I suggest Access Reports first as they're easy to create and make look pretty.
Each ENTITY (ie. HOTEL, CLIENT, etc.) will have certain information about it, that someone will need to view/edit.
For Example:
CLIENT - to send out a bill, you'll need an Address and Name
RESERVATION - You'll probably need the Room number, and the dates that the reservation is valid for. As you will be sending out a Bill for a reservation, you'll need the Client to send it to.
And so forth...
This should get you started with an idea of what you need to do. This is by no means the only way to get started with an application, but it works for me. Incidentally, this is what a Analyst writes and is usually called a Specification.
Hope this helps,
Kieron
____________________________
Build it better, faster, quicker, easier.. then fix it (non-offical MS mission statement)
|