Thanks Mike, I got my fields, so everything is fine!
>The only automatic to detect that a row was changed is with a timestamp. Sadly, the timestamp has nothing to do with dates and times. It's just a rolling number.
>
>Most people add two columns to the row like updatedOn and UpdatedBy, which are filled in by either a trigger or explicit code.
>
>-Mike
>
>>I'm not sure I understand -
>>
>>In my VFP screen I'd like to inform the user that the data from the SQL server table that (s)he's looking at was last updated at 2002.10.10 22:00
>>
>>There is no row in the table that could provide this info, and I have no influence on the DB design, so I'm not likely to get one.
>>
>>>Either create a trigger to update a column on the row or have your stored procedure do it.
>>>
>>>-Mike
>>>
>>>>There's bound to be a way to determine the date / time of the latest update to a table, and I did search, but so far with no luck.
>>>>
>>>>So, help is truly appreciated.
>>>>
>>>>TIA
>>>>
>>>>Peter
Peter Pirker
Whosoever shall not fall by the sword or by famine, shall fall by pestilence, so why bother shaving?
(Woody Allen)