DB layout advice

Viewing 1 reply thread
  • Author
    Posts
  • February 13, 2011 at 2:25 AM #3299

    harringg
    Participant

    I’ve already created two databases with Tap Forms eliminating the need for two other stand-alone apps for that content.

    I’m now working on an Auto log DB and am following the Trip Log in the Tap Form Manual as a guide. This is for creating a table that will have all four cars, and their specs (Tire size, wiper blade size, VIN, etc…) and then a second database as a link-to-form with repair log (date, milage, cost, part, etc…) and a maintenance log (oil change, wiper replacement, etc…). I’m not looking to use it to track fuel consumption.

    Does this seem logical?

    Auto (Main DB)

    VIN

    Year

    ..

    ..

    Tire Size

    Maintenance Log (Hidden Link-to-form)

    Repair Log (Hidden Link-to-form)

    What I’m hoping to achieve is to be able to view a running total of a given vehicle using the Calculation option under Edit Form and then filter on a given auto.

    Ie.

    Honda, Oil change:$30, Wiper blades: $15, Headlight: $10

    Honda: sum=$55

    Nissan: Oil change: $35, Air filter: $25

    Nissan: sum = $60

    Is this possible?

    Or should I have 6 DBs? One for each car, two for the log DBs?

    February 13, 2011 at 8:05 PM #4405

    Brendan
    Keymaster

    Hello Harringg,

    I think what you’e proposing would work just fine. You would have just 6 records within the same Auto form, one for each vehicle. Then the linked fields can have their own calculation which would show you the totals just for the items for each selected vehicle.

    Thanks!

    Brendan

Viewing 1 reply thread

You must be logged in to reply to this topic.