Saving data to Lookup

[Bill Akers]

Nancy Palmquist wrote:
> Shuman, Mike wrote:
> 
>> System:  Windows XP Pro
>> filePro Ver.  5.0.09DN9
>>  
>> Situation:
>>  
>> Input process does lookup into transaction file to obtain
>> transaction number.  Process adds "1" to transaction
>> number and writes it back to lookup file.
>>  
>> User can break out> 
> Do not assign numbers from @wlf logic.  That requires that you move to 
> that field to make the assignment and ESC can be pressed anytime.
> 
> You can use the BREAK OFF, logic to keep them from cancelling when your 
> data is out of balance or incomplete.  This can force them to complete 
> the record or press ESC to run the exit logic as shown above.

I am a day late getting into this thread, but might be helpful.
I wrote a program for an industry that was regulated by sevaral law 
enforcement agencies and required(unequivocally) that the transaction 
numbers be sequential with no skips in the sequence. In fact a store 
manager was booked and put in jail becasue their software(different 
vendor) "lost" trnsaction numbers when a transaction was voided. Proper 
warnings had already been issued by law enforcement that the condition 
had to be remedied.
The way I handled the sequential numbering was to  turn BREAK OFF as 
Nancy suggests, assign a temporary number for header/line item linking 
until the transaction was ready to acquire permanent status. When the 
final printout was made the permanent transaction number was assigned. 
Then if the transaction needed to be reversed, there was a procedure for 
voiding with a status change to show that that transaction was a voided 
transaction. This transaction could not be deleted, and neither could 
the other transactions that were assigned permanent transaction numbers. 
The transaction was indeed stored with a status of void. Since this was 
a multi-user system, that was the only way I could find to prevent 
skipped numbers or duplicates. Rolling back was not an option because of 
the possibility that the number might be 2,3 or even 8 or 10 numbers 
behind tha last number already used because of the speed with which 
transactions were processed

> 
>>  
>> Thanks ahead of time for any ideas.  
>> Michael L. Shuman
>> Technical Support Specialist, DBA
>> Plant Protection & Weed Control
>> Kansas Department of Agriculture
>> mshuman at kda.state.ks.us
>> 785-862-2180
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>>
> 
> 


-- 
William P. Akers          E-mail: billa at mgmindustries.com
                           Web Site: http://www.mgmindustries.com/