Marc : >> I would love to have a comp,I think your file would help me. Sometimes I add 2-3 cols to a tab, add a view, change a view, change the length of a field... It sure gets hard to remember all of these little changes and make a command file to "update" the users data base. I have some offices that either didn't get our updates for the last 2 years or didn't know how to run them. There has been so many changes since them I have been worried about sending them one big upgrade. Would your program take care of this? <<
Yes, but you have to apply a strict organisation : - have the client's version number in his DB (old) - identify the new version (the one you send) - have an install program that apply the DB structural changes between the 2 versions. To be sure I don't forget anything, each I change the permanent tables' structure (add/delete column ...) I change my INSTALL.CMD file. This file is sent with the new empty DB. During install process, INSTALL.CMD apply the changes. You must take care of clients who don't install the new version (because they forget, they are lazzy ...). With this method, they can skip 1 version : the next version will install correctly. No problem for views, forms, reports .... as they get a full updated DB. No problem with TEXT columns that become bigger. If you wants to see what INSTALL.CMD looks like, send me your private Email adress ... Problem is that all comments, messages ... are in french. Best regards, J.M. GRATIAS, Logimatique
