Renoir,

From an architectual view, I'd say that keeping you business rules layer in a data centric programming language (like VFP) makes more sense than trying to do this in a low level language like Java or .NET. It might pay off when business rules are less static. You can store the business rules in a table, and process them in VFP very clean and quickly. This is much harder to do in .NET or java technologies.

In very much the same way we have build a HL7 parser: Code in a table, that might be different for each and every client for each and every message type, without having to compile.

Walter,


>We are looking towards moving everything away from Foxpro and towards a new technology. Probably over 3 to 5 years. These are the layers we initially outlined:
>
>Presentation Layer - Thin client and some thick client (browser-based, Java, C#).
>Application Server Layer - Handle requests from Presentation Layer and outside sources (Java or C#).
>Business Rules Layer - Interpret requests and return/update data in the Data Layer (Java or C#).
>Data Layer - SQL Server or Oracle.
>
>Any very general recommendations as to whether C# or or Java would be better choices? Is there a right and wrong combination of languages across the layers?
>
>Looking for some very broad thoughts here.