In <[log in to unmask]> [log in to unmask] writes:
 
> 1) MS Access needs a unique key, because it was designed that way.  But who
> cares, it would not know a unique key from a hole in the ground.  Just use
> any old column and tell MS Access that it is a unique key.
 
I'm no odbc expert, as we're just starting to experiment with it ourselves
(and also ran into the unique-key requirement problem in MS Access), but I
wonder if a way around it wouldn't be to have HP automatically generate a
pseudo-item for every detail dataset - say a numeric field which gets
initialized to the Image record# of the record... Ignore updates to that field
when records are being updated but use it as an index if possible. Seems like
that field could then be used as (or made part of) the unique key for MS
Access?
                Just a thought...
 
                      Chris Bartram