Garren.Shannon
Member
- Local time
- Today, 15:52
- Joined
- Sep 22, 2022
- Messages
- 113
Hey Pat... Something just hit me that, to be honest, I should have thought of before but didn't. I have all the master tables located on the SQL server like ,dbo-drivers, dbo-Vehicles, etc.. I also have the off-line version of those tables copied to the local drive. In my entire build of this thing, I save the VehicleID and DrvierID numbers as reference for the trip. When uploaded to the master table, the data should reflect the same driver and vehicle numbers but if the keys on the local DB ever get out of sync, then the master DB won't know how to locate which driver or bus the trip was referring to. For example, if I add a new driver to the master table, how can I make sure all the local tables have the exact same matching ID number for that new driver if the local index ever got out of sync?The batch ID passed to the central app ends up being two part. part1 is the driver or the vehicle. part2 is the generated sequence number. Do not concatenate them. Doing that just makes it harder to work with the fields.
To correct this, should I stop storing the ID in favor of the Driver name and the vehicle name? Or should I delete the local driver db, and import the master DB every time the user is uploading data to the master to ensure the keys between the master and the local tables match?