Sami, Javier, Thanks, I'm sure that I didn't restore an older version but having reloaded the "corrupt" forms from my backup I can tell that the damaged ones had all been edited recently - from changes I made since the backup being lost.
Thinking back as well, I know that I deleted rows from the Dos Sys_Forms table because I no longer use any Dos forms. Strangely, some of the "corrupted" forms that I have used - rather than tried to amend - actually worked. It was only when I tried to edit using another of them which insisted on starting the forms module that I knew there was something wrong. I can only assume that somehow the RB4 file got corrupted - and not necessarily by R:Base. Maybe if I get time I'll play with one of my backups that shows the problem and see if I can find a way to correct it because it looked as if all the data was there - just not gettable at. Regards, Alastair. ----------------------------------------------------------------- Since all the forms and reports for the Windows version of R:BASE are stored in the RB4 file, perhaps you did a restore from a backup of the files and didn't include the RB4 file and it referenced an older version... Or created one if it didn't find one ... I've never had an indication that there was corruption in the RB4 file, but I guess it could happen. Sami ----------------------------------------------------------------- Sami Aaron Software Management Specialists 19312 W 63rd Terr Shawnee KS 66218 mailto:[EMAIL PROTECTED] 913-915-1971 > Alastair: > As you know, you can have forms with the same name under DOS and Windows. Is > it possible that the Windows forms were deleted (or corrupted) so Rbase > could not find them and thus went looking for the forms in the SYS_FORMS > rather than the SYS_FORMS2? I have something similar happen to me when I > started working with the Windows version; now, whenever I convert a form or > report I rename it adding a W_ in front, so the "emp_form" under DOS becomes > W_emp_form under Windows. When you display the forms in the designer, you > can easily see which forms are DOS and which ones are Windows. > The only problem I have had with forms and reports is when you modify a > report/form (saved under the latest release) with a previous release it > tends to corrupt the form/report. I run into this problem when I load > forms/reports developed with the latest release in a clients computer which > doe not have the latest patch, the forms/reports run fine, but if you try to > modify them (with a previous release), many time they become corrupted. Now, > I make all the changes in my computer (with the latest patch) and upload the > modified forms/reports. > Javier, > > 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] Behalf Of Alastair Burr > Sent: Wednesday, February 26, 2003 12:22 PM > To: RBASE-L Mailing List > Subject: [RBASE-L] - Form problem (was: Ping - Pong) > > If Only! > > Actually, I just had a weird experience with about a dozen forms in one of > my databases: > > For some reason they suddenly decided that they were not really v6.5++ forms > and wanted me to convert them to the latest (available <g>) version. 3 or 4 > were originally from the Dos version but in name only having been completely > reconstructed and the others were originally constructed in v6.5++. > > So I did the conversion - as there was no way into the form without doing > so - and that lost me part of the formatting of the fields and EEP data. Not > good! > > Anybody have any experience of this happening or any idea why it might > happen? > > Luckily I had a backup that didn't seem to have the problem but it was my > oldest backup - I don't keep too far back as things change so much that it's > not (usually) worth it. Perhaps now it a good time to write a procedure that > unloads each form (and reports) to individual files rather than rely on the > reloads and backups that I already do. > > Regards, > Alastair.
