Here, here - I, too, miss the ability to "tweak" the sys_forms/reports tables. Mind you, it was always a risky business so a good backup was essential beforehand.
I've only gone back to an earlier version once and that was to an earlier patch to prove to myself that something worked in the older one but not in the newer one. It's something to bear in mind, though, if a test in an earlier version is needed. But we'd do that on a copy of the database, wouldn't we <g>? Thanks & regards, Alastair. ----- Original Message ----- From: "Javier Valencia" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, January 04, 2003 6:34 PM Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build 1.862 > Alastair > I run into a problem with a report that whenever I tried to run it or modify > it, it would crash the system in a manner pretty similar to the one you > describe with your forms. I believe that the corruption happened when I > tried to modify it with an older release after it had been saved using a > later release. I seem to recall a thread a couple of months ago that dealt > with this subject. I deleted the report, rebuild it and the problem was > gone. I imagine that you may have the same problem with your form, you may > try restoring it from an old backup and the updating it, or rebuilding it > altogether. I miss the old SYS_REPORTS and SYS_FORMS files where you could > go and do some "selective surgery" to the report code itself, I never run > into a problem that I could not fix by going into these files and making the > changes by hand (or is it manually ,,,what I mean is without using the > designer). > I have learned my lesson and once I update to a new release (patch) I do not > go back to an older one. I still have 2 "corrupted" reports to rebuild but I > am feeling lazy today... > > Javier Valencia, PE > President > Valencia Technology Group, L.L.C. > 14315 S. Twilight Ln., Suite #14 > Olathe, KS 66062-4571 > (913)829-0888 > (913)649-2904 FAX > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alastair Burr > Sent: Saturday, January 04, 2003 12:19 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build > 1.862 > > I'm in W98SE and more often than not I have to re-boot but I usually do > anyhow. > > I'm seriously considering putting Crashguard back in, though, it used to > catch about half the crashes that I'm getting now and then I was able to > save data and exit cleanly. At the moment every crash means losing > everything that's not been saved which in turn means a reload at least if > not a return to a backup. I'll try and hang on for a few more days just to > see if anybody else turns up a solution. I really thought that the clickable > images was going to be the answer as I think I can probably say most crashes > occur when forms using them are or have been or are about to be in use. > > Maybe this particular form is just corrupted and needs to be re-created but > that's a long job but maybe I'll have to bite that particular bullet. > > Regards, > Alastair. > > > ----- Original Message ----- > From: "MikeB" <[EMAIL PROTECTED]> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > Sent: Saturday, January 04, 2003 3:59 PM > Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build > 1.862 > > > > If you are working in a Win9x environment, after a couple of crashes, I > > would "Absolutely" reboot the machine before continuing (you can't be > > assured that that OS is cleaning up and reclaiming a possibly corrupted > area > > of memory that "May be Required" to perform the operation). > > If you are working in an "NT" kernel environment, I would "Probably" > > reboot..... > > > > > > ----- Original Message ----- > > From: "Alastair Burr" <[EMAIL PROTECTED]> > > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> > > Sent: Saturday, January 04, 2003 10:39 AM > > Subject: [RBASE-L] - Re: Criteria For MyUnstablenessWithR:Base6.5++Build > > 1.862 > > > > > > > Following Razzak's indication that the buttons on a form only work with > > BMP > > > images - contrary to all the documentation - I amended the form that > > seemed > > > to be giving me the most problems. > > > > > > First of all, there is no obvious way of knowing what image, certainly > > image > > > type, that is used by a button. I have 5 buttons with with 5 JPG images > so > > I > > > created BMP copies then went to the form to change them: > > > > > > Object Manager | Forms | [select form] | Design > > > Left Click on button (to ensure it IS selected) | right click on > > Properties > > > | Left click on Load Image | select the new BMP version | click on Open > | > > > click on OK. > > > > > > Did it load the new version - who knows, it might have or it might not > > > have - I have no idea. The image is the same so there is no visible > > > difference. > > > > > > Repeat for the other 4 buttons but the third one crashed R:Base when I > > > clicked on open. > > > > > > Start again and save the form between each change of image. Third one > > > crashes R:Base again. This button is the same size as all but one of the > > > others in dimensions as well as file-size. > > > > > > Start again but commence with "difficult" button - R:Base crashes. > > > Start again as before - same result. > > > Move the old JPG images out of the directory so they cannot be used. > > > Start again - manage to save the form this time but R:Base crashes when > > > closing the form designer. > > > Start again - create a new button and open the new BMP image - at last > > save > > > it and exit without crash. > > > Repeat with new buttons for other four items. Save form ok but R:Base > > > crashes on exiting form designer. > > > Start again, go to form designer and move an item a fraction and back > > again > > > then save form and exit without crashing!!!!!! The new buttons all have > > > their images and they must now be BMPs. > > > Rename and then reload the database - no errors. > > > Exit R:Base and remove the "pause for 2" from the app before the edit > > > command. > > > Start R:Base with the app - still crashes. > > > Put the pause back in then give up and go to the pub - it's Sunday. > > > > > > Regards, > > > Alastair. > > > > > > > > >
