Can you point me in the direction to find out more about this please?

>It may make sense to develop a rules engine. I worked once for a company that made medical coding systems. They relegated all the decision stuff to a rules engine. It had to be updated every three months, but because all the rules were encapsulated in a single DLL, it made the updates easier.
>
>>Hi Thierry,
>>
>>I appreciate your and others' recommendation against a rewrite. I fear the project myself. Our motivation for a rewrite is the long term lack of VFP developers.
>>
>>The problem our app solves is calculating payrolls according to the laws of Panama, which is a complex set of rules that periodically change... to become more complex. The need to solve this business problem is practically eternal, so the useful life of the rewritten program is potentially very long, assuming we keep it current, and we feel it will pay off.
>>
>>We know the business problem well, better that our competitors, and the smallness of the market makes it unattractive to foreign software companies. We believe we have a few years to complete the rewrite. During that time we will cover our flanks by developing a few add on options with West Wind Connection, mostly report oriented with some data capture. Right now our app is 100% LAN.
>>
>>We need to make good choices, so I'll be asking many questions:
>>
>>We'd like to make the rewrite fairly data driven, so the first question is: Does .NET allow the equivalent of VFP's EVALUATE(lcCommand) ?
>>
>>Thanks for the concern and response.
>>
>>Alex