Ray -

In another message topic, you stated:
Quote:


That brings up a couple of points for me:

1)  I have frequently needed to press F3 TWICE to delete a record.  If memory serves me right, it usually happens when I am in search mode and advanced to a "blank" record (usually containing date last modified) which I want to delete.    Is this expected behavior?  (If I use F9 to go back a record, then as far as I can tell the "blank" record is saved).

2) If I do use NotifyForm(4) then how can I easily delete the record should I consciously decide that I want it gone?

I noticed NotifyForm(0) to allow saving.  Would this make it easier to save a record?  For example, if I modify a record and then switch to search mode, I get a warning that the record has not been changed and have to select Navigation/Save Record before I can proceed (which is a nuicance). 

If NotifyForm(0) will not "fix" this problem, then I want to again request that the option to leave a record be changed.  Instead of asking "Do you want to continue (without saving the record)" I would like to have the option to (1) continue without saving the record OR (2) SAVE the record and continue.

Thanks!

Ray -

Quote:


I understand.  So, my next question is:  Is there a way to delete the "blank" record without bringing up another "blank" record that I have to delete?  The bottom line is that I would like to press F3 once and be done with it.  

Quote:


I am not saying that is is a "problem" (per se) that you do not automatically save changes --- although I personally would very much prefer it.  This is especially true, if we could have an "undo" option so that we could revert to the original record, in the event an unwanted change was made.

But, what I am saying is that it is clearly a nuisance to have to go through so many clicks - to simply do what I want in the first place and there has to be a better way to deal with this.

Coincidentally, here's exactly what I was doing when I was notified of your last reply to this message.  

I made a change to a record and wanted to retrieve another reocord.  So ....

1.  I pressed F7

2.  I had to then press "No, I don't want to close this record."

3.  I had to then press Navigation to open the menu options.

4.  I had to then press Save Record to save my changes.

5.  On this attempt, I pressed save record once and "it didn't take" so I was back to Pressing F7.

6.  I was again back to (#1 above), having to press "No, I don't want to close this record."

7.  I then had to press Save record twice to get it to actually save the record.

8.  I had to press F7 (twice) to get to where I wanted to be in the first place -- which is retrieve spec mode.

Even if save record had "worked" in step 4, I still would have had to make 4 or 5 clicks to simply save the record and switch modes.  In either case, I think this is an extraordinary amount of extra effort to simply save a record and change modes.  So, once again I would prefer:

1) automatic save with a simple "undo" option.

2) failing the automatic save, my original request for one click to save the record (or not) and advance to the selected mode.  Something like:  "Your changes have not been saved. Do you want to save them before closing the record?"    Yes   No

Thanks for forwarding my original request for future consideration.  I would appreciate it very much, if you would also forward these additional comments.

I would also appreciate hearing from others on this issue.  Surely, I can't be the only one who finds it so annoying.  And, in the unlikely event no-one finds it annoying, I would like to know whether anyone sees any problem with my alternate suggestions.

Thanks!

Ray -

I had completely overlooked the "save application" icon because I want only the record to be saved.  Nevertheless, that might come in handy, so thank you for pointing it out.

As for the automatic save option, it is clear that you and I will never see eye-to-eye on that but that does not change my feelings about it.

I am NOT saying that the form should be saved any time an element is changed (and I can see where that would cause a slowdown).  I AM saying that it should be saved when you are "closing" the form by taking some other action (other than Shift/F7).  This is typical of most other databases, including MS Access.  Any time you leave a record, it is automatically saved.  In addition, you can click anywhere on the left column to save a record at any point.

As for "how far back to go" how far back does Shift/F7 go?  Ideally, I would like to see progressive undo's so that each undo would reverse the last action taken element by element, etc.  If that is not feasible then - in my opinion - it should revert to the status of the record when it was opened.

In a "best case" scenario, if I "give up" and try to train myself to ALWAYS (ugh) save a record before I leave it, I still have to:

1)  Click on Navigation (TWICE - because it wasn't focused)

2)  Click on Save Record

3)  Click on F7 (TWICE - in spite of the fact that the menu was focused and, perhaps, because the focus was on a different section of the menu.)

Even if I got accustomed to this, I would still find it annoying because I would have to do this every time I changed a record.  In the normal process of "updating" a database, this is done over and over and over again.

OK Ray -

First, to address your suggestion about a command button, I had already thought of that and still don't like the idea of being "forced" to save each record.  Granted, though, it would still be better than what I currently have and I guess I should try it.

But, what about another way of dealing with this issue?!

It is a "given" that any company offering a product/service needs to satisfy as many customers as possible.  Certainly - as a whole - I see an earnest effort to incorporate changes requested by customers and you all should certainly be applauded for that.

In this case, it seems that if I am satisfied, you (and as a user of the database, also a "customer") might not be happy with the change.

So - what about a change that could satisfy everyone?  What about incorporating a "global" type option and let each individual user decide.  This would be similar (I would think) to the Application Default Path settings where each user decides what his or her own path should be.  Provide an application "default" where the user can choose whether or not to provide automatic saves.

If the user chooses no, then let the program function as it currently does (except for changing the option to close the record - to provide the option of closing the record with or without saving the change).

If on the other hand, the user chooses yes (to automatic saves) then save the record and allow the user to "move on."

Once again, I would appreciating your incorporating these additional comments with my original request, for the designer(s) to consider.

Thanks!