Hi,
That's not exactly what I had in mind. Let's say I generate a report and import it into my database. At the moment, each record can only be identified by a subset of the data in its row(For eg. date, time, project, etc).
If I were to go back and edit the time record on my Ipad and import it once again into my database, I want the record in my database to be updated, and not create a new record. This is difficult to do at the moment because some of the data that I might use to uniquely identify a record may have changed. This is where a UID would be useful. It wouldn't change. This would allow me to keep a consistent set of data throughout the process.
Thanks