Hi Nadya,
How about this (off the top of my head):
lparameters pcField, plBatchMode
local llSuccess
llSuccess = .t.
if llSuccess or plBatchMode
llSuccess = Test1(parms) and llSuccess
endif
if llSuccess or plBatchMode
llSuccess = Test2(parms) and llSuccess
endif
if llSuccess or plBatchMode
llSuccess = Test3(parms) and llSuccess
endif
if llSuccess or plBatchMode
llSuccess = Test4(parms) and llSuccess
endif
etc.
return llSuccess
>Hi everybody,
>
>We have this situations. On the record level we cal a function, which has the same name, as a table+"Tr" at the end. Say, PropMstrTr.
>
>The syntax of this function is like this:
>
>lparameters pcField
>=Test1(parms)
>=Test2(parms)
>=Test3(parms)
>=Test4(parms)
>etc.
>return .t.
>
>If Test1 fails, it invokes another function (general), which logs info into LogTable, etc.
>
>Validation could be run in batch mode, or can run interactively using a form.
>The problem is, after Test1 fails, we want to return to a Form and don't run other tests. Do you know, how can we make it happen?
>
>My original suggestion was to use this syntax:
>Test1() and Test2() and etc. , but as I understand, in batch mode we want to perform all tests and log all errors. So, this idea would not work.
>
>The program itself should not care about modes, etc., IOW, code in the program should remain.
>
>Do you have ideas to help us?
>
>TIA.
If we were to introduce Visual FoxBase+, would we be able to work from the dotNet Prompt?
From Top 22 Developer Responses to defects in Software
2. "It’s not a bug, it’s a feature."
1. "I thought I fixed that."
All my FoxTalk and other articles are available on my
web site.
Unless specifically identified otherwise, anthing posted here is purely my opinion and may or may not reflect the policies or practices of Microsoft.