Timestamp vs. Tables with Posted Values...

Ok, here is situation. I made a “cache” table for all posted (and non-posted) sales, credit-memoes, and return receiptes… i have stored procedures that goes something like this: For posted values, get last timestamp from another kinda config table and then get all posted data that has timestamp bigger than this value. For non-posted data, Delete everything from cache table and than reload from non-posted tables. tables for posted data that i watch are Sales Invoice Header and Sales Cr.Memo Header (and ofcourse, their children, SIL and SCML) After a while of testing, i notice that some of Sales Invoice Header records changed their timestamp values. I’m pretty sure that clients didn’t changed SIH records through object designer and neither did I. So, Navision itself did it. Does anybody knows why he touched them? what could be a reason that navision will make modifications on tables that holds Posted values? I forgot to mention… Ofourse, Navision is on MS SQL 2000 and timestamp field is sql-s field…

Number of printed copies?

hm… let me check it, it could be one of the reasons…

phuh… although that field isn’t one that made me a problem, it sure could in a future… thanx… So, my Timestamp algorithm is kinda buggy isn’t it? phuh… that makes it harder to do it :frowning: