@ud doesn't catch what you'd think it would

[Scott Walker]

> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+scottwalker=ramsystemscorp.com at lists.celestial.com] On Behalf Of
> Mike Fedkiw via Filepro-list
> Sent: Wednesday, September 24, 2014 8:23 PM
> To: 0 Filepro List
> Subject: @ud doesn't catch what you'd think it would
> 
> So after all of this, I decided to check something, it seems as though
> all the 09/15/14 dates on the reports were probably accurate because I
> was dropping all of the thems that were tagged deleted. When I went
> looking into the invy file through IUA, I was starting at the beginning
> of the file, like record #1 but that file is so old, everything I looked
> I saw with different dates were actually tagged deleted now and not
> included in the report.
> 
> Now I have no idea exactly what process I may have run that actually
> updated everything on 09/15/14 but apparently something I imported or ran
> updated all of the active items @ud on that day.
> 
> As for the useless @ud field,I just tried adding a few items to an
> invoice and then took a look at the items through IUA in the invy file.
> Guess what, the @ud field didn't change at all. BUT, if i actually change
> something on that record from within IUA, I see tha @ud instantly change.
> 
> What use is the @ud if it can't catch changes to the records in a file.
> 
> All I do when I change something like the on hand is do a lookup to that
> inventory record and then something like invy(97)=invy(97)-xinv(20);write
> invy;return, well something like that anyway.
> 
> Thanks for all of the reply's today, at least it helped me figure out
> that I was going in a direction that's just a dead end for what I needed.
> 
> Mike
> 

Mike,

Also check @bd which is the last batch update of the record.

So by check @bd and @ud you can get anything that was directly update today by a user and anything that was batch updated today by some process.

Regards,

Scott Walker