>I have a form that has a data environment that has all the tables in my DBC. I have auto open tables turned on, which it does quite nicely. I'm using the Microsoft's textbutton class and when I go to hit "Save" on the Add/Save button, I get trigger failures on the "child" tables because it ran their update before it ran the "parent" table update. The problem seems to lie in the textbutton updaterows method. In this method, it grabs the table names in the order that they are opened and then does a do loop in that order to run tableupdate(). Has anyone noticed this before? Is there a way to dictate the order that the tables are opened in without hard coding it? Thanks!
>
>Laurisa Watkins
>Seattle Parks Dept.
Laurisa,

I wrote an article in an issue of Foxtalk a few motnths back that explains how to handle this problem. It does it by building and array of the open cursors and then sorting that array ofn parent child lines as well as putting views before tables in the array order. It them sworks throught that array to do the updates.

You might try chceking out with FoxTalk at 1-800-788-1900 to see if you can get a copy of the issue that contains the article named a"A Classy Way to Save Changes".