Search results

Solved in terms of I used an older backup of the test database and the problem went away. Unsolved in that I never determined what the error was with the BE file that was giving me the error. Stepping through code - yes, see above, although it didn't seem to be on a specific line. If got...

@gemma-the-husky - Yes, typically, I would want to find the cause and solution. In this case reverting to a past version of the BE cleared the error, so I'm not super worrried about it - as I said, it was prototype/test data anyway. @The_Doc_Man - You are probably onto something, SQL is not my...

@Pat Hartman - Thank you again for the assistance. In this case, I don't really care. This was just dummy data that I was using to test Data Macros and code upgrades before we release the production database. I just started from the original backup copy and ran you DDL Conversion program (took...

The other thread was talking about an error when saving records (that I worked around with Me.Dirty = False) and some good info on validating input and which event to use, but did not address this issue and I was told to start a new thread. I'm okay with ignoring the error, if that is what you...

More info. I only get the error on one particular form. I have 7 forms in the database with similar code that do not produce the error. I tried compacting the front end and that didn't make a difference. I was initially getting the error when I deleted a record I had just created, but I...

Initially posted at: https://www.access-programmers.co.uk/forums/threads/audit-update-of-a-field.329588/page-10#post-1909410 I'm getting this error when deleting a record using a delete button control: Stepping through the code under the delete button, the record is deleted, the code steps...

Wrong thread, but I'm getting a new error when I delete a record: Stepping through the code under the delete button, the record is deleted, the code steps through the Form_Current() event, updates the custom navigation buttons, and then returns to the delete button code and displays the error...

It works for us, but it's a bit more complicated than I said ... - Essentially, I'm doing the same thing as in this thread - possibly incorrectly as in the linked thread: https://www.access-programmers.co.uk/forums/threads/beforeupdate-vs-afterupdate.270219/ As an example, let's say my field...

New issue - this is more of a WHY question - it seems to be working the way I intended. I have a user table and I am using Yes/No fields to show "rights" for each user - i.e. if this box is checked, the user can do certain things. I adapted the UserName Code from the previous replies, so the...

The validation code is in the Field_AfterUpdate events - we didn't used to have any. Essentially, Form_BeforeUpdate looks like this: If DontPromptUser = True then Exit Sub If MsgBox("Do you want to save?", vbYesNo + vbQuestion, "Save Record") = vbNo Then Me.Undo End If...

@Pat Hartman - I think we are saying the same things ... I don't call it pushed, but ... I have a global Boolean variable called DontPromptUser. If the user changes a field, the background of the field is changed and the SAVE button is enabled. If the SAVE button is clicked, DontPromptUser is...

Clarification: I already have code that if the record is "dirty/changed" and the user tries to go to a new record, the database will show a pop-up and say "Do you want to save the record?" I also have a button to manually save. If I press the Save Button, I get the error message, but I DON'T...

Actually, it seems like the save IS working - i.e. I don't get the prompt to save the record when I go to a new record and the changes are saved, but I get the error message and none of the code after the save line runs. (I could probably avoid using Me.Dirty = False by trapping for Error 3939...

Save is behind a button. When the button is clicked, it runs down to the DoCmd.RunCommand acSaveRecord line. Then it runs the Form_BeforeUpdate() code, then it runs the Form_AfterUpdate() code, then it returns to the button code - the button is named UPDATE and the event is UPDATE_Click()...

It SEEMS to work fine if I change: DoCmd.RunCommand acCmdSaveRecord to Me.Dirty = False Not sure WHY or why that is required now, but ....

Okay - I changed all the DDL strings to "text(x)" and updated the back end from the original version. I no longer get the odd behavior with spaces padded to the right of the field I added to the text box on the bound form. However, now when I click the save button to manually save the record...

I'm not sure about that ... I used DDL with CHAR(255) and I was using a text box on a User From to display the current value of the field on the bound form and paste the new value. The value I tried to add was about 25 characters long and Access said the text was too large for the field. I...

@Pat Hartman - Thank you!!! The code that you are using was text(50) or text(255). That seems to be working. Somehow, that wasn't working for me, and I looked up code that suggested CHAR(255). That works, but it makes the field length AS 255 instead of UP TO 255 characters. I'm changing all...

I have some DDL questions now ... I confused myself reading these links: https://stackoverflow.com/questions/25300821/difference-between-varchar-and-text-in-mysql...

Minor point, but it's tripped me up a few times so far. If you are editing the DM files using the User Interface (Access, not Notepad II), the changes are made similar to AfterUpdate on a form. i.e. if you change a field, you MUST click enter of click in a different field before saving. If you...