Results 1 to 5 of 5
  1. #1
    Join Date
    Sep 2003
    Posts
    5

    Transactions of Database

    Hi All,

    I am creating an dB for an assignment, in Access and one of the elements I have to do is to describe the transactions of the dB.

    The database that I am assembling is a Car Dealership, which has many dealers, many suppliers. The tables that I have are -

    - Dealer
    - Car
    - Suppler
    - Order
    - Employee
    - CarDetails
    - Customer
    - CarProfitMargin (I decided to take the "CostPrice" and SellingPrice" out of the "Car" table and create their own table).

    Can anyone recommend what transactions could be derived form this database? I am having difficulty understanding this...

    Regards,

    Darren

  2. #2
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171

    Re: Transactions of Database

    Sounds like "transaction" is being used here in the sense of "business function". These would be things you can do with the data, e.g. "Hire Employee", "Order Car", "Deliver Car", "Cancel Order", etc.

  3. #3
    Join Date
    Sep 2003
    Posts
    5
    Yeah, Here's one I am thinking of -

    Inventory: In the database, when a sales rep sells a vehicle, there will a an update transaction in place which will automatically update the inventory at a particular dealers and subsequently, in the overall groups inventory of vehicles.

  4. #4
    Join Date
    Sep 2002
    Location
    UK
    Posts
    5,171
    Right, so the transaction is something like "Sell vehicle", and all the other activity you described will be an intrinsic part of that transaction.

  5. #5
    Join Date
    Feb 2004
    Posts
    1
    Hi,

    I also have a similar DB to create and I've done a few of them in the past.

    From reading on different forums, I found that the "proper" way to manage inventory DB was not to update the stock everytime it changed but rather use an stock in/out table to keep track of the quantity.

    Basically, when you need to know the stock qty, you run a query calculating how many were purchased, how many were sold, and you get your number.

    I've programmed DBs using both systems and can tell you that using an update system can get very messy. The worst case being if the customer finds a way to run a certain transaction twice (and they will...), the inventory numbers don't match anymore and you can't really figure out why.

    It would be great to have feedback on this as I have another inventory DB to do and I really want to do it the right way...

    Pharkas

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •