G
Guest
I'm sure most of you gurus can help
I am pretty good at figuring out the best way to design a relational database, but I'm sort of hitting a road block. My local firearm licensing officer wants me to design something in access for him to keep track of gun owners, etc. No problem.
But he wants this to be on his desktop and laptop and have them "sync" up, so the newest data is in both places. Problem is, I'm not 100% sure how to approach it, and it's not good if I accidently lose these types of records. I did some lurking and saw stuff about dirty records, and flagging them as "new" records, so I'd know which ones to copy. Would this be a way to do it, or is there a much better way? TI
Joe
I am pretty good at figuring out the best way to design a relational database, but I'm sort of hitting a road block. My local firearm licensing officer wants me to design something in access for him to keep track of gun owners, etc. No problem.
But he wants this to be on his desktop and laptop and have them "sync" up, so the newest data is in both places. Problem is, I'm not 100% sure how to approach it, and it's not good if I accidently lose these types of records. I did some lurking and saw stuff about dirty records, and flagging them as "new" records, so I'd know which ones to copy. Would this be a way to do it, or is there a much better way? TI
Joe