Hi Albert, & thanks for the offer - Randy Peterson ditto. Following Razzak's message I've checked the History demo and can see what I presume is RBTI's "standard" method of using multiple buttons is what Javier pointed out just beforehand. It's getting late here now so I'll try that tomorrow.
Just for the record, the problem is not that I can't get the buttons to work with my eep - they work fine - once I get into the form. R:Base sometimes crashes or hangs just before getting into the form. I'd be happy to use the "standard" method but all I suggested was that _maybe_ my codelocked eep was the problem _if_ it had some sort of error that R:Base was finding as it entered the form. My eep may not be the best way and I'm happy to change it to see if that stops the crashes. Also, don't forget that the form may not be the problem at all. I'm making an assumption that as a pause immediately prior to the edit using command generally means there's no crash that it's the form that the cause. From other people's comments that seems to be likely - but not proven by a long chalk. I said a while ago I was almost ready to make some statement on the problem but it's still not clear enough to me to say anything that I'd like to stand by. However, I still have some suspicions that others may like to confirm or deny: Firstly, screen resolution. I'm using 1280x1024. I also use 1024x768 for playing DVDs. Sometimes I don't bother to change back from the lower resolution and I suspect that there's a difference in the number of times R:Base crashes. I don't do it often enough to be sure but I get an inkling, a feeling, that the lower resolution is less trouble. I can't think of any reason except that there should be less memory needed. I've got 256mb and the graphics card is a good one (Matrox) with 16mb of its own memory. Secondly, my original form 6 months ago started with text buttons which I changed to images once I was happy with everything. When I changed them back to text last week (or whenever) I noticed some strange combinations of text in the newly revealed button text box - different from that which I had typed when they were first text buttons and not the same as the image filename. Maybe, just maybe, virgin image buttons are fine but changing from text to image or vice versa is not to be recommended. I sure that I've had less problems with the restructured form but I still get some crashes without the pause just before calling it. Perhaps the pause gives the hardware time to draw the screen, perhaps it gives R:Base time - I don't know, I'm not the expert, I'll happily admit to making mistakes, I'd love to help the others who've had similar problems, I don't care if it's my (our) fault or a bug or whatever the cause turns out to be. I hope that it's something really simple, stupid even, but I hope that the end result is a better R:Base because if, between us, we can nail this problem, then v7 can avoid duplicating it should it turn out to be a bug (of some sort) or if there's a few people with red faces then I'm sure we're big enough to live with that and let others learn from those mistakes. Thanks to everyone who's made suggestions, Regards, Alastair. ----- Original Message ----- From: "Albert Berry" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Monday, January 13, 2003 9:30 PM Subject: [RBASE-L] - Re: Fw: [RBASE-L] - Fw: [RBASE-L] - Re: CriteriaForMyUnstablenessWithR:Base6.5++Build 1.862 > Alastair - I have a set of forms on forms that I use in a scheduling application. If you want some samples, I can forward a db copy to you with multiple forms on forms using the syntax RUN <filename> USING <text>. > At the top of the eep, > SET VAR %1 TEXT > SET VAR vOption TEXT = .%1 > SWITCH (.vOption) > > etc. >
