>>>Craig, I think we're talking about two different things here.
>>>
>>>< The validation routines run on the server. >
>>>Not in what I'm describing...the validation routines run *between* the VFP client and the back end server. They are *not* stored procedures...in fact, they would execute IN ADDITION to any stored procedures.
>>>
>>
>>
>>Someplace, a computer has to exist where the business rules actually run. Either the client, an application server, or the data server. I was curious as to where?
>
>Okay, Craig, now I understand your question (I think <g>).
>
>The actual executable DLL for this thing could reside either as part of the client (ie, running on the machine that runs the client) or on an application server somewhere that's known to the client (where a number of clients could instantiate it...the more common approach). The data the executable DLL uses to do its thing (the rules themselves) can reside one of three places: built into the DLL as an included table (you might use this for canned or stand-alone apps), as an associated table which the DLL knows where to look for it (the normal approach), or on a data server somewhere that the DLL knows about or can use views to gain access.
>
>If I still don't understand your question (which is entirely likely <g>) and you're going to be at DevCon, catch me there and I'll show you how it works.
>
>Evan Pauley
Nope...I understand perfectly. I've known for a long time how this kind of stuff works, just wondered how you were doing it in your specific implementation. I plan to use VFP 6.0 and MTS to do this on an application server in the future.
I will be at DevCon. Maybe I'll catch you there.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer