Alastair, watch out for having SNAP TO GRID turned ON when editing reports and forms. Sometimes things move when you least expect them to. I have had this happen to me, usually when I try the lasso and change the height of a group of objects.
I have also noted, in RBW 65++, that the grid does not necessarily stay in the same place relative to the form top margin when you scroll up and down. "Alastair Burr" <[EMAIL PROTECTED]> wrote: >Hi Dennis, > >I think for about the first time I'm going to _almost_ disagree with you: > >I haven't seen it happen lately but I _think_ R:Base does tell you at some >point if fields are outside the margins - maybe somebody else can confirm or >deny this. I now know that it doesn't _always_ tell you - so perhaps that >ought to be fixed. > >It wasn't all that hard a problem to find either - I just had to look _off >the screen_ to the right where _I knew_ nothing was wrong before. It was >immediately obvious that the field(s) crossed the right-hand margin. What I >didn't expect was for it to make any _real_ difference when output was to a >file. Correcting it was easy and the obvious thing to do/try. What might be >a harder problem is, as Bob Thompson pointed out, if the field is just >_touching_ the margin. > >However, what I do think is wrong is that I didn't get any error message - >just one of the many crashes that I've been used to over the last 2 years >using RBW. Over the last few months I've reduced the number of crashes >significantly (no need to repeat all that again here) but this was obviously >linked to a few reports so I could hunt for the cause. (Incidentally, >Norton's CrashGuard allowed me to recover R:Base and run the reports as if >nothing had happened - so it does have its uses - for those of you who don't >like it.) > >What would have been much better is a nice message long before running the >report that the margin was too narrow. >What still worries me is how the margin changed - assuming that I wasn't >stupid enough not to move it on at least 3 reports when I have moved it on >many others. As these reports were working and suddenly started crashing I >have to assume that, at least to start with, the margins were set correctly. > >Regards, >Alastair. > > >----- Original Message ----- >From: "Dennis McGrath" <[EMAIL PROTECTED]> >To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> >Sent: Wednesday, August 20, 2003 2:14 AM >Subject: [RBASE-L] - RE: The impossible seems to happen > > >> Sure seems like this little "gotcha" should be adderess by the RBTI bug >> team, NO? �Something so difficult to find should be found bay the >> system and fixed/reported. My opinion. >> >> Dennis McGrath >> >> >> >> >> >> --- Thompson Technology Consultants <[EMAIL PROTECTED]> wrote: >> > Hallelujah! >> > >> > Alastair you are a life saver! �I too was printing the reports to a >> > file. (PDF) >> > This "Invalid Date" error was causing me to go absolute nuts! �I >> > could find >> > nothing wrong in my code, variables or report for that matter and it >> > would simply >> > popup this "Invalid Date" error completely at random. >> > >> > Following your lead below, I looked at my two reports again, >> > especially the >> > right margin. �Low and behold I had ONE field that the very edge was >> > on the >> > margin line. �Not over it, but on it. �I relocated the field back to >> > the left a few >> > pixels, ran the program and NO ERRORS! �I ran it multiple times and >> > again >> > received NO ERRORS!. �This thing was going to cause big problems and >> > thanks to you it is now fixed. >> > >> > One strange thing however.... the field that was "on the margin" was >> > a >> > page number field and had nothing to do with a date. �Strange that it >> > gave an "Invalid date" message. >> > >> > Anyway, thanks again and this is a great example of the benefit of >> > the list. >> > >> > Bob Thompson >> > Thompson Technology Consultants >> > >> > >> > -----Original Message----- >> > From: Alastair Burr [SMTP:[EMAIL PROTECTED] >> > Sent: Tuesday, August 19, 2003 12:16 AM >> > To: RBASE-L Mailing List >> > Subject: [RBASE-L] - RE: The impossible seems to happen >> > >> > I don't suppose this is the cause of your problems but it might be a >> > "heads >> > up" for others: >> > >> > I have recently - ie: it hasn't happened before - had problems with 2 >> > or 3 >> > reports that caused R:Base to burp noisily. >> > When I first checked the reports I could see nothing wrong but they >> > are all >> > reports that I print to a file and have a wide right-hand margin. >> > When I >> > scrolled over to the far right - just in case - I found that one, or >> > more >> > fields crossed over the margin. Naturally, moving the margin further >> > to the >> > right so all fields were inside solved the problem. >> > >> > Now, I don't think I'm stupid enough to not move the margin when I >> > placed >> > the fields so something changed them. It may well be that something >> > quite >> > legitimate does this, or I did something stupid, or there's some >> > circumstance that might do it - an R:Base crash when the form is not >> > saved - >> > whatever. >> > >> > Either way, it seems that the margins are important even when >> > printing to a >> > file which users may not expect. >> > >> > Regards, >> > Alastair. >> > >> > Using latest RBW 6.5++ >> > >> > >> > ----- Original Message ----- >> > From: "Thompson Technology Consultants" <[EMAIL PROTECTED]> >> > To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> >> > Sent: Tuesday, August 19, 2003 1:32 AM >> > Subject: [RBASE-L] - RE: The impossible seems to happen >> > >> > >> > > I have a similar problem while printing a report that is inside a >> > cursor >> > > (pointer). �I get a random >> > > "Invalid date" error. �Out of a data set of 30 "loops" it will >> > appear >> > > anywhere from the >> > > 2nd record to the 22 record. �No change in data or anything. >> > Simply run >> > > the program >> > > multiple times and it gives the error at different records. >> > Records that >> > > run fine without >> > > error one time will produce the error on another run. �The program >> > does no >> > > updating, >> > > simply prints two reports for each of the 30 customers. >> > > >> > > This sounds like a related issue, but alas I have found no >> > solution. �In >> > my >> > > case, I only >> > > have one date field- InvoiceDate - and searching it is easy. �I >> > found no >> > > invalid data. >> > > Reloads or packs did not help. �The report was originally driven >> > off a >> > view >> > > and I >> > > even changed it to temporary tables, but with no improvement. �(No >> > > improvement on >> > > the error, but speed was significantly improved!) �However I still >> > get >> > this >> > > random error. >> > > >> > > Troy's mentioning to go away from a While loop is interesting. �Is >> > there a >> > > known >> > > issue with pointers or While loops? �This is the third time someone >> > has >> > > suggested >> > > not using a pointer. �I ask because I use Declare Cursor statements >> > quite >> > > often. >> > > >> > > Sorry I cannot assist with an answer, but had a few questions of my >> > own. >> > > >> > > Thank you, >> > > -Bob Thompson >> > > >> > > -----Original Message----- >> > > From: Michael Moser [SMTP:[EMAIL PROTECTED] >> > > Sent: Monday, August 18, 2003 10:19 AM >> > > To: RBASE-L Mailing List >> > > Subject: [RBASE-L] - RE: The impossible seems to happen >> > > >> > > Hi Troy, >> > > >> > > I thought it might be a memory issue but it seems to be data. �It >> > will >> > > happen on the first loop if I restrict the pointer to a record that >> > causes >> > > the problem but I can not determine why the same variable condition >> > with >> > > data from that record will evaluate as False at one point and True >> > a few >> > > lines later ... �can memory leak show up on the second pass of a >> > while >> > > loop? �I will try switching to a go to and let you know ... at this >> > point >> > I >> > > will try anything ... >> > > >> > > :-} >> > > >> > > Thanks for the tip, >> > > Michael Moser >> > > EXAQ Micro Services >> > > Phone: 916-768-7656 >> > > Fax: 916-966-8313 >> > > >> > > �>> �This is probably a memory leak issue related to a while loop. >> > > >> > > �>> �Try changing your while loop into an IF statement and a GOTO. >> > > >> > > �>> �Troy >> > > >> > > �>> �-----Original Message----- >> > > �>> �From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of >> > Michael >> > > �>> �Moser >> > > �>> �Sent: Monday, August 18, 2003 9:46 AM >> > > �>> �To: RBASE-L Mailing List >> > > �>> �Subject: [RBASE-L] - The impossible seems to happen >> > > >> > > >> > > �>> �Hi all, >> > > >> > > �>> �Here is a mystery that I have been beating my head against a >> > wall >> > > with. >> > > �>> �This code processes about 8,000 records just fine then, with >> > about >> > > 2,000 >> > > �>> �records to go, goes into a infinite loop where variables have >> > to have >> > > the >> > > �>> �same value but do not. �if I reverse the sort order, the >> > problem >> > > happens >> > > �>> �after about 300 records. >> > > >> > > �>> �P800, 512MB Ram, Windows XP Pro, R:Base 6.5++ 1.864xRT03. >> > > >> > > >> > > �>> �Suddenly the second while loop starts evaluating as False, >> > even >> > though >> > >> === message truncated === >> > > -- Albert Berry Full Time Consultant to PSD Solutions 350 West Hubbard, Suite 210 Chicago, IL 60610 312-828-9253 Ext. 32 __________________________________________________________________ McAfee VirusScan Online from the Netscape Network. Comprehensive protection for your entire computer. Get your free trial today! http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397 Get AOL Instant Messenger 5.1 free of charge. Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455
