last update using get next from a different file

[Richard Kreiss]

Top post. 

I still hold with my windows comment. I have always added at least 2 fields to hold who Nast updated a record and when. There have been times that I post the process bane rather that a user name especially if I am having odd data showing up in a record which can be updated from different programs. 

Just an aside. !@ub or *@ub could be added to a browse in the file rather then a screen allowing for looking at a lot of records at once. 

Richard
Sent from my iPhone

> On Sep 24, 2014, at 6:01 PM, Mike Fedkiw via Filepro-list <filepro-list at lists.celestial.com> wrote:
> 
> Well, It seems as though the @ud  simply does not work when exporting records. I changed the processing so I could do the output directly from the invy file and the @ud is still stuck on 09/15/14(the first record found @ud) for every record after too. I also went into the invy file using IUA and scanned through a bunch of them. Pretty much every record that I saw had a different @ud date.
> 
> The @rn record number works just fine though, I don't get it...
> 
> 
> 62  -------   -   -   -   -   -   -
>      ◄ If:
>      Then: invfile(26)=oh
> 63  -------   -   -   -   -   -   -
>      ◄ If:
>      Then: invfile(27)=@rn
> 64  -------   -   -   -   -   -   -
>      ◄ If:
>      Then: invfile(28)=@ud
> 65  -------   -   -   -   -   -   -
>      ◄ If:
>      Then: invfile(29)=hl
> 66  -------   -   -   -   -   -   -
>      ◄ If:
>      Then: end
> 
> Mike
> 
> 
> On 9/24/2014 5:25 PM, Mike Schwartz wrote:
>>>> On 9/24/2014 4:02 PM, Mike Fedkiw via Filepro-list wrote:
>>>> Okay I get what invy(@ud) is but since it returns the exact same date
>>>> for like 20+ thousand records and that's just impossible in my system,
>>> No, "lookupname(@UD)" returns the update date for the *current* record
>>> in the lookup file.  Add "!@UD" to a screen in the other file, and browse
>> it in
>>> dclerk.  See what it shows.
>>> --
>>> Kenneth Brody
>>      If Mike used getnext to do a lookup into some other file, doesn't the
>> getnext open that record in update mode?   And wouldn't that always return
>> an @ud with today's date in it?
>> 
>>     Or doesn't @UD get updated until some of the data in the record gets
>> changed?
>> 
>>     Or doesn't @UD get updated until the record is released by the next
>> getnext?
>> 
>>      I'll put this on my bucket list to test.  Let's see:  That puts it
>> around February, 2094, if nothing on my list preempts it...
>> 
>> Mike Schwartz
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: ddd.jpg
> Type: image/jpeg
> Size: 287596 bytes
> Desc: not available
> URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20140924/189275ad/attachment.jpg>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list