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

[Kenneth Brody]

On 9/24/2014 8:22 PM, Mike Fedkiw via Filepro-list wrote:
> 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.

So when I asked you to check @UD in the "invy" file to see if it really was 
"09/15/14", you didn't actually check the records that were being selected 
for the export?

> 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.

Sounds like it.

> 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.

Updates made through LOOKUP set the @BD field.

[...]

-- 
Kenneth Brody