Editing data in datasheet view

[arichins]

I have an data entry form, and an idea to put a subform underneath it, that has a record of everything that particular user had entered in the past x number of days, so that they could review-edit what is in the system. They need a way to review and edit, but this will make it easier on them than a search/edit due to the small volume.

Problem is, Access is acting tottally bizarro when I try to edit the fields. The form's source is a table, and the controls are linked to that table, simple set up.

For example, when I try to edit, sometimes Access will just ding at me like the field is locked, then I'll try other fields and it will work, then I go back to the field that was previously not working and it works, then I go back to another field and it will only let me type in 5 characters for no apparant reason (it does does not match the table length). I'll go back to it later and all of a sudden I can type in more than 5.

This platform is the ADP architecture by the way. I'm the only one using this form/table right now, and I haven't been able to find a pattern to what it's doing...it's just sorta random.

 

[music_al]

is the database small enough to upload ? If so, attach it and I'll take a look

 

[arichins]

I figured it out, it's another one of those "stupid things". But you have to double click on a field in datasheet view in order to edit it. Otherwise, it will just ding at you. So it was working whenever I happened to double click the cell.

Another thing though, is that if you double click a cell with multiple words in it, it will only highlight the word you are on, and Access won't let you get beyond that word, you have to delete the rest of the string by using the delete key, then continue on.

For example, if I had the string, "God save the Queen" and double clicked on the beginning of the cell, it would highilght God, and I'd only be able to type 3 characters in, to replace God. It would not continue on to insert or over-write the rest of the string. I'd have to press the delete button to get rid of "..save the Queen", so I could continue on.

Considering this quirks, I wonder if MS didn't spend much time making datasheet view good for editing data. But it's nice to have a simple way for them to edit and delete data.

 

[arichins]

By the way, how did you Brits like my "God save the Queen" quip?

I'm actually American(or Yank as you'd call me), but this is the first forum that came up when I searched for an access programming so I joined.

I think your country is really neat by the way, except of course, for your government, which is as corrupt as ours.

 

[MSAccessRookie]

By the way, how did you Brits like my "God save the Queen" quip?

I'm actually American(or Yank as you'd call me), but this is the first forum that came up when I searched for an access programming so I joined.

I think your country is really neat by the way, except of course, for your government, which is as corrupt as ours.

For the record.

While I am truly glad that this Forum has assisted you, there are a few Special Forums that have been set up for Cultural and Political excanges (WaterCooler and Politics & Current Events are two that quickly come to mind), and such exchanges should be avoided in the Technical Forums whenever possible.

 

[music_al]

still sounds like you have a problem with your form though.... err Mr Yank

God Bless America

 

[arichins]

Sorry, this is still a technical thread, that was just an aside. I didn't know being personal in this thread was like talking in church. But you Brits don't go to church anyway....oops, I"m doing it again!

I did figure out what is wrong with editing the datasheet. But now the form is inserting a null record every time I close it, even though I'm using a close command button, with the following code:

DoCmd.Close acForm, Me.Name, acSaveNo

I have other forms that do not do this, now now I can't figure out what setting I've got miss configured to cause it to do this.

 

[boblarson]

Just an FYI for you -

in the code:

DoCmd.Close acForm, Me.Name, acSaveNo

the acSaveNo has to do with DESIGN CHANGES, not records. If you don't want to save changes you would need to use the Before Update event to cancel

Cancel = True
Me.Undo

but you should probably address why something is dirtying the form anyway, even if you aren't wanting it to.

 

[arichins]

Just an FYI for you -

in the code:

DoCmd.Close acForm, Me.Name, acSaveNo

the acSaveNo has to do with DESIGN CHANGES, not records. If you don't want to save changes you would need to use the Before Update event to cancel

Cancel = True
Me.Undo

but you should probably address why something is dirtying the form anyway, even if you aren't wanting it to.

Thank you Bob! You're not going to try to cast any demons out of me are you? Sorry, couldn't resist that one.

I will try that code. I just wonder why it's doing it on this form and not the others. But what do you mean by "dirtying the form"?

 

[boblarson]

But what do you mean by "dirtying the form"?

When a bound form has something start to add, delete, or edit information on it, the form becomes "dirty" and that means that something is going to try to be saved, whether it be new data, old data that has been changed in some way, or data that has been deleted and is now going to be removed.

 

[arichins]

I learned a new word, "dirtying the form". I figured out what the problem was. On the "form Current" event, I was setting the default value of some hidden fields. This was causing the form to become dirty. I also put in a cancel button a user can press to prevent a record from being written to the DB.

 

[boblarson]

Glad you got it sorted.