I am using A5 V10.5. I have buitl a couple of A5 databases, one desktop (DBF) and one web based (using SQL tables). I developed a database in Alpha Four that has been running for over 20 years. My projects are few and far between, so when I need to develop a new database, it is like starting the learning curve from scratch. I recently took some advice from Tom Giles (thank you Tom) who gently persuaded me to attempt this project using A5 DBF as opposed to SQL (back-end tables). I have done little coding with Xbasic, but have a halfway decent understanding of coding and have used Action Scripting.
That is a bit of my background, showing I am a relative newbie and often need expert advice. Now to my project.
I am developing a database using A5.DBF. This DB tracks service calls on devices, parts used in repair of those devices, movement of those devices between different sites, and both cost of parts and shipping costs.
Scenario: A device fails onsite and requires service. The options are, a part is shipped to site for onsite repair by a tech, or the device is shipped back to the repair depot. In most cases, when a device is shipped back for depot repair, a replacement device must be sent to the site (minimizing downtime). Once the failed device sent to depot is repaired, it becomes a spare unit available for shipping to another site as a replacement. There are around 15 remote sites, so it is easy to see how a single device (tracked by serial number) can move around to different sites over a period of time.
What I need to do for a failed device:
- Create a work order ticket (WOT) with associated multiple service activities
- The use of multiple parts for repair must be attached to the associated service activity, or activities
- Track the movement of, and current location of each device(about 150 devices right now, but will grow to around 500 in a couple of years)
- Track cost of all repair parts used as well as shipping costs
I have tables and relationships set up for the handling of the work order ticket and associated service activities. I am pretty sure I have tables created for all of the data I will need.
My big issue is creating history tables to track locations, movements, part usage and costs. Building these table relationships are more of a challenge than I have previously encountered. I am not looking for a total solution, but perhaps, some expert experience and knowledge to fire a spark of creativity in me that is lacking due to inexperience. Any help would be appreciated. I hope I have not been too vague.
Thanks,
Mike
That is a bit of my background, showing I am a relative newbie and often need expert advice. Now to my project.
I am developing a database using A5.DBF. This DB tracks service calls on devices, parts used in repair of those devices, movement of those devices between different sites, and both cost of parts and shipping costs.
Scenario: A device fails onsite and requires service. The options are, a part is shipped to site for onsite repair by a tech, or the device is shipped back to the repair depot. In most cases, when a device is shipped back for depot repair, a replacement device must be sent to the site (minimizing downtime). Once the failed device sent to depot is repaired, it becomes a spare unit available for shipping to another site as a replacement. There are around 15 remote sites, so it is easy to see how a single device (tracked by serial number) can move around to different sites over a period of time.
What I need to do for a failed device:
- Create a work order ticket (WOT) with associated multiple service activities
- The use of multiple parts for repair must be attached to the associated service activity, or activities
- Track the movement of, and current location of each device(about 150 devices right now, but will grow to around 500 in a couple of years)
- Track cost of all repair parts used as well as shipping costs
I have tables and relationships set up for the handling of the work order ticket and associated service activities. I am pretty sure I have tables created for all of the data I will need.
My big issue is creating history tables to track locations, movements, part usage and costs. Building these table relationships are more of a challenge than I have previously encountered. I am not looking for a total solution, but perhaps, some expert experience and knowledge to fire a spark of creativity in me that is lacking due to inexperience. Any help would be appreciated. I hope I have not been too vague.
Thanks,
Mike
Comment