[AccessD] "Faked" replication

Hi Steven

> Therefore, I'm going to bite the bullet (and forego additional fees) to backtrack on my database design. It will end up where the home office will do no data entry at all, just collect information
> from the field units. Since each field unit is at a different Customer site, that may simplify the assigning of keys. I'm not real thrilled about using "random" AutoNumbers. Regular AutoNumbers
> aren't any good either because of the various data entry locations all needing to be merged at the home office. It appears that the natural hierarchical key would be: Corporation, Division,
> Location, Department, JobPosition...that is, five key fields for each record. The records hold ergonomic information about an industrial employee's work environment. Yes, there'd be all that extra
> baggage being hauled around in each record, but no chance that there'd be any duplication. 15 different Departments could have a JobPosition like "Hod Carrier", but as long as they were in
> different Departments !
>  there'd be no duplication.

> Is this sensible? Should I snap out of it and use random AutoNumbers?

You could choose to use GUIDs for autonumbers ...

/gustav