Bryan Carbonnell
Bryan_Carbonnell at cbc.ca
Thu Jun 12 07:00:35 CDT 2003
Kath, Did you run beuDBAisDBUptodate before you added the second mod? If so, you need to increase the version number for the second mod. Once the BEU hits the first mod in a version that is marked as being applied it determines that the upgrade for that version has already been done. If it you tried to do both mods at the same time and it didn't do the second mods, have a look at the error log in the FE directory. THat may give you some clues as to why it didn't work. Failing all that, if you want, you can send me the error log, the following two tables: tblDBAModifyDatabase tblDBAModifyDatabaseMods, and the version number in tblDBAversion and I'll see what I can see. You can send them to bryan_carbonnell at cbc.ca Bryan Carbonnell bryan_carbonnell at cbc.ca >>> SDSSoftware at Optusnet.com.au 11-Jun-03 7:42:03 PM >>> Hi everybody - I have just started using the BEU tool. I clicked on 'Insert mod' and added my first modification, which was table, add field. field = directorname txt, size 75 to tblx. I then clicked on 'new mod' to add the same modification for a different table, ie. to insert a new field of the same name. I made a call to the beuDBAIsDBUpToDate routine and now find that it only made the first modification, not the second. When I go back into frmdbamain it shows the first modification as applied, but the second not. Now I cannot get that second modification to happen. When I re trigger the beuDBAIsDBUpToDate routine it appears to ignore the 2nd mod. (I have manually added the field myself to check that the field name / size etc is Ok and then undone that manual change). Since these 2 mods have to go into my production version early next week, any tips?