>>#defines are useful. Don't think you will be albe to get rid of the macros
>>
>>Where's the fun in taking somebody else's code ?
>>
>>The fun is in making it, although in this case other emotions may be involved in the process
>
>I don't think I would be able to come up with such elegant approach on my own. I don't see a problem of re-using good code which is public domain and just modify it to suit my needs. I always give a proper credit (or I hope I do). Why do I need to re-invent the wheel? < g >

Well those things take time to write.
When I wrote mine it cost me over a week. I had the sample vfp standard code to get the original feel and borrowed some ideas from it. I rewrote most of it a couple of months back. It's about 950 lines now (core part, including a lot of blank lines) and is table driven, ie I keep all relations, tags, index expressions in an internal table (updated every so often).
When the database gets opened I create an object with multiple arrays (Customer_D[], Customer_I[], CustomerU[]).
When a trigger is fired, it gets the corresponding array and executes all things it needs to (eval(array[ i ]))

I also have the possibility to (table driven and loaded into an array) execute (what I call) actions before and after the RI part and that is the nice bit (for me)

I think that every one with a reasonable amount of foxpro experience (and you have that) can write that. The fun is in visualizing how it should work and breaking it down into manageable pieces. And you come out stronger and more experienced, Nadya

I may look at someone else's wheel, I confess, but I'll always use mine (that is learning the hard way)

cheers,