The app I'm working on uses VFP triggers to allow or prevent changes based on the existance of a particular object to ensure the changes are being made thru the system (don't start me on the wisdom of that...I inherited this mess). We are trying to migrate the system to use SQL Server 7.0 as the back end, and the powers-that-beat want to carry over this design "feature".
Unfortunately nothing comes immediately to mind. We have already build a class that passes changes to SQL directly. It wouldn't be too difficult to create a middle-tier COM object to handle data changes, but can a SQL Server trigger communicate with an external object? Anyone have any suggestions on how to do this?
Dan LeClair
www.cyberwombat.comSET RANT ON - The Wombat BlogLife isn’t a morality contest and purity makes a poor shield. - J. Peter MulhernDisclaimer: The comments made here are only my OPINIONS on various aspects of VFP, SQL Server, VS.NET, systems development, or life in general, and my OPINIONS should not be construed to be the authoritative word on any subject. No warranties or degrees of veracity are expressed or implied. Void where prohibited. Side effects may included dizziness, spontaneous combustion, or unexplainable cravings for dark beer. Wash with like colors only, serve immediately for best flavor.
