Dear Tom, Razzak, MikeB & everybody who has read these posts with interest:
Before anybody gets upset it might be worth making a few, hopefully, salient points. Tom obviously believes that something has changed in the latest beta. I've had the same experience with something quite different with a report in the previous beta where an older beta worked and the newer one didn't. This was resolved by RBTI and is now mentioned in the latest beta documentation. Like Tom, I've also questioned forms in the latest beta and found a "work-around" that may be the "right" way to do something or it may be due to a change _somewhere_ in R:Base that nobody has seen as the cause of the effect. From the sound of it, I still think that mine is a very similar effect to Tom's - not the same, but similar. Of course, we could both be doing a similar thing the same wrong way. The point is that we all want R:Base to work the best way it can. Working with a beta version almost has to make you think it's the beta version that's wrong rather than anything else. It's in the very nature of the beast. There's not really a lot of point in testing it if you don't try and find out where there's something wrong. Further, and almost by definition, every tester has a different level of expertise so will present varying levels of problems. At the same time, just because nobody else has spotted a "bug" doesn't mean that there is no bug. There may be or there may not be. When they're obvious it's much easier to fix them but not every bug is going to be the result of an obvious change. One of the problems is not knowing what has been changed apart from fixes to known problems and new features. One one hand it would be much easier for beta testers to have a list of all the changes so that they know where problems might occur. On the other hand that might lead to missing other problems. What nobody wants is for a patch to be issued as an update and for there then to be a problem - and especially a problem that was spotted and dismissed, for good or bad reasons - prior to release of the patch. To prevent anybody falling out with anybody else - let alone for the sake of the product - would it not be worth a phone call between RBTI & Tom to see if there's something that can be done to resolve the problem? Assuming, of course, that's not already been done. Just my twopennyworth, Regards, Alastair. PS: I created a small test database (200kb zipped) which I used to resolve my form problem. I'll happily make it available if it could help in any way. ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
