another cracking article, again. "you are spoiling us.":)
My query regards the use of the replica id. I would consider this a piece of
data and would not like to hard code it.
I think maybe a custom data base profile form/document would be of use for this
data with a field for rep id. Your shared field could compute on that value
instead. That way if the replica id changed then it would not call for a design
change (which gives version,upgrade and admin headaches) But all that required
would be to edit a document, making admin of the db easier.
Hi Jake,
another cracking article, again. "you are spoiling us.":)
My query regards the use of the replica id. I would consider this a piece of data and would not like to hard code it.
I think maybe a custom data base profile form/document would be of use for this data with a field for rep id. Your shared field could compute on that value instead. That way if the replica id changed then it would not call for a design change (which gives version,upgrade and admin headaches) But all that required would be to edit a document, making admin of the db easier.
What do you think ? Regards ant.