Jan,
I don't know what kind of problems you have encountered, but here are some suggestions: 1. I always keep the original installer of Rbase available 2. Also I am keeping the last update before available. 3. In case you are encountering problems you have the possibility to go back to the last update by reinstalling the original installer followed by the update before the new one 4. Then restore the original database and everything should be ok 1. Make a backup of your current database a. Supposing there is no structure change - which is highly unlikely - I don't see any advantages in your proposal. Unloading in the old version and reloading it again in the new version will have no effect on the 'normal' tables. b. In my opinion the most vulnerable part of the database, forms, reports and so on, are stored in so-called blobs and I don't think you can avoid problems by reloading them. Maybe I am wrong, but that's what I think (btw I am not a real technical guy). 2. Install the update and do some tests to find out everything still works fine. I must say, generally speaking, I seldom do have problems with an update of Rbase. Hope this helps a bit in your thinking about a solution for your problem. Tony From: [email protected] [mailto:[email protected]] On Behalf Of jan johansen Sent: donderdag 12 april 2012 17:27 To: RBASE-L Mailing List Subject: [RBASE-L] - Applying updates Ok. I had some weirdness show up when I applied the 3/17 update. I want to avoid that for the 4/10 update. Is the best procedure to do an unload all of the database (not the best term), apply the update and run the all file? Jan
