Our practice is that business rules and processes are separated into several methods. Usually, we have a separate button for posting, addition, deletion, reports, save, restore, etc. In the click event of each button, we call the equivalent custom method. That way, you have more control of what the application is doing. Advancing it further - one step forwared, we are currently converting every business rules from custom method, which is VFP specific, to COM components to make it more flexible and scalable long term.


>Hi Jess,
>
>Can you suggest a place or method to check the HIST TABLE
>to make sure that the data hasn't been posted, before I attempt to
>post to it twice ?
>
>John
>
>SET DEFAULT TO \EFG
> SET SAFETY OFF
> SET TALK OFF
> SET ECHO OFF
> SET DELETED ON
>
> *** USE pay IN 0
> SCAN FOR ins_co_nam = "AMERICAN UNITED LIFE" AND group_code = 'A01'
>
> REPLACE paiddate WITH THISFORM.TEXT1.VALUE,;
> fromdate WITH THISFORM.TEXT2.VALUE,;
> todate WITH THISFORM.TEXT3.VALUE,;
> servfee WITH .69
>
>
>
> REPLACE balance WITH amt_pre - servfee,;
> duecompany WITH balance posted with "P"
>
> *** REPLACE servfee WITH 0, percent WITH 0
>
> ENDSCAN
>
> SELECT * FROM test, pay WHERE test.ss_numb = pay.ssnumber AND pay.ins_co_nam;
> = "AMERICAN UNITED LIFE" AND pay.group_code = "A01" and AMT_PRE > 1 INTO Cursor;
> CuReport ORDER BY test.last_name
>
> IF _TALLY > 0
>
> *BROWSE
> REPORT FORM payment3b PREVIEW
>
> inResponse = MESSAGEBOX("DO YOU WANT TO POST THIS DATA FOR A01/AUL TO HISTORY?",36,"E.F.G. POSTING OPTIONS!")
>
> IF InResponse = 6
>
> ***LOCAL loProgBar
> SELECT pay
> ***loProgBar=ProgBar()
>
> SCAN FOR GROUP_CODE = "A01" .AND. INS_CO_NAM = "AMERICAN UNITED LIFE"
>
> *** loProgBar.npercent=RECNO()/RECCOUNT()*100
> SCATTER MEMVAR MEMO
> INSERT INTO hist FROM MEMVAR
>
> ENDSCAN
> MESSAGEBOX("DATA FOR A01/AUL HAS BEEN POSTED TO HISTORY.","E.F.G." )
> ENDIF
> USE IN PAY
> ELSE
> MESSAGEBOX("FOUND NO RECORDS THAT MATCH YOUR REQUEST")
> ENDIF