Then, is this an endemic issue or only common to Win7? I have never experienced this (XP).
----- Original Message ----- From: "Bruce Chitiea" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, June 14, 2012 9:27 AM Subject: [RBASE-L] - RE: Form Designer: EEP Edits: Save Failures:Solved Correct and Correct: 1. Glad that the underlying dataset is read only, or there'd be smoking craters all over my database after each of my form-design sorties; 2. Custom EEP changes are NOT saved between form designer sessions UNLESS the form is test-RUN while WITHIN the form designer session in which the changes are made. Granted, it's good practice to RUN before exiting anyway. Thanks, Bruce -------- Original Message -------- Subject: [RBASE-L] - RE: Form Designer: EEP Edits: Save Failures:Solved From: "Mike Byerley" <[email protected]> Date: Thu, June 14, 2012 4:41 am To: [email protected] (RBASE-L Mailing List) I thought he (Bruce) was making changes to the EEP in the form, saving the form, exiting, then reopening the form and the EEP changes weren't being saved. I thought from the description of the answer he posted, that he was instructed to run the form while in the designer before exiting and that would save the changes to the EEP. That's what I thought I read. I didn't understand, from the description that the underlying dataset while in the form designer wasn't being saved, as I understand that has always been read-only. ----- Original Message ----- From: "A. Razzak Memon" <[email protected]> To: "RBASE-L Mailing List" <[email protected]> Sent: Thursday, June 14, 2012 12:55 AM Subject: [RBASE-L] - RE: Form Designer: EEP Edits: Save Failures:Solved : At 10:39 PM 6/13/2012, Mike Byerley wrote: : : >Inquiring minds would like to know why this is so... : : FWIW ... : : While in Form Designer, running or previewing the form [Ctrl+F9], the : underlying dataset is always Read-Only! : : Very Best R:egards, : : Razzak. : :
