>I would assume that CT is suggesting that your validation is done with a middle tier VFP COM object that other applications could call. The would give you 'EnterPrise Wide' validation.
You're right, he talks about taking advantage of automation servers. I guess my question here is more of a 'what if' scenario. Like I said, I really like the approach in this article but what if the client feels strongly about their ownership of data in my VFP app's dbc, and want access to it through a commonly known M$ Office tool like excel or < duck > Access. So even though ODBC might not be optimal, I thought is was a valid concern if I'm going to store my business rules in a table like Blankenship describes. I guess what I'm getting at is that this seems like a really good technique, so why does it feel like I'm leaving data unprotected?
Roxanne M. Seibert
Independent Consultant, VFP MCP
Code Monkey Like Fritos