At 11:08 AM 12/4/95 -0500, Eric Schubert wrote: >The strategy would be to keep indexes intact as long as possible with a >planned "restart" break point. However, I was only proposing time stamps >for synchronizing foreign systems. Your introduction of other data (user, >etc.) requires modification of Image, like you said. Ah, then yes, I agree that if your goal/intent is limited to the application of foreign system sync, then this model should work adequately and be easy enough to implement as a feature of a TPI system. And for many sysadmins this would be very useful functionality, though not for me, since for now my databases are conveniently self-contained. And as to your other comments, I agree that it is unlikely we would see in our lifetime a fundamental re-engineering of the Image file structures to support such things as internal timestamping or user-stamping for broader purposes. We can always dream, though... :> ----------------------------------------------------------------------- Jon Diercks -------- mail: [log in to unmask] Programmer/Analyst /|| | chat: powwow:[log in to unmask] Computing Services /_|| | WWW : http://rowlf.csv.anderson.edu/ Anderson University / ||__| tel : (317)641-4305 Anderson, IN 46012 -------- fax : (317)641-3851 o________________________________________________________ ___ _\_, \=`==^==> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^