<< About the stored procedures, I keep my source files in a separate directory and have code to reload them whenever I wish. This has worked fine for me. >>
I do the same although I keep the PUT code in a comment inside each stored procedure, so it's a little more tedious to add all the stored procedures back into the database. However, I feel that if you backup a database with UNLOAD ALL and reload it, you should get back an identical, working database. What happens now is the SPs are missed and any command establishing a TRIGGER in the database (which _are_ included in the UNLOAD) fails. If we're going to maintain our own structure files, why bother UNLOADING STRUCT? All we'd _really_ need from the database would be data. In addition, I just had the following happen -- I had to rebuild a database. I went into my SP directory and added back all the stored procedures. What I didn't realize, however, is that one of them had _not_ actually been installed in the production database -- it was old code. Adding it back by accident caused all INSERTs into the relevant table to fail (it was a Trigger). Yes, I could have gone into my stored procedure loading file and removed the code for that procedure. But all the information to unload and restore the stored procedure is actually in the database -- why not use it? -- Larry
