Ms Access Continuous Form Dont Show Last Blank Row
Unless the form is read-only, there will always be a blank new record at the end of the form.
When you delete the last real record, focus will be on the new record - is that what you see?
---
Kind regards, HansV
https://www.eileenslounge.com
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Hi,
Thanks for you response.
No, if there is data in the record before the new (blank) record and I select that record and click on my command button the current record is stil there but all the data is blank. The New record is still below my now blank record.
I also tried this code:
If (MsgBox("Are you sure you want to remove this Record", vbYesNo, "Remove Record") = vbYes) Then
DoCmd.SetWarnings False
RunCommand acCmdDeleteRecord
DoCmd.SetWarnings True
End If
I got the same results.
I have the same code in another form and it works fine. There must be something in this form that is creating this problem.
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
That's strange - it shouldn't happen.
You could try adding a line
Me.Requery
above the line with End If. Does the empty record disappear?
---
Kind regards, HansV
https://www.eileenslounge.com
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Thanks again,
I already tried that and the blank record goes to the top of the form because of the form sort.
I don't get it.....
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
I don't get it either - I'd have to see the database to say more about it.
---
Kind regards, HansV
https://www.eileenslounge.com
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
What is the forms' RecordSource? it may be that, if it's a query, the query is still returning a row even though a row from a table has been deleted. If the controls in the form are bound to a column is in the table from which the row is deleted, then this would account for the row with empty controls.
_____________________ "Don't write it down until you understand it!" - Richard Feynman
Ken Sheridan,
Cannock, England
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Ken, in that case, don't we usually see #Deleted in all the bound controls?
I suspect that zipone has some code somewhere that's setting a bound control to Null or ""
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
in that case, don't we usually see #Deleted in all the bound controls?
That would be the case if the row had been deleted from the form's recordset but the form not requeried. What I'm wondering is whether the RecordSource is a query using an OUTER JOIN and a row is being deleted from one of the tables, but the query is still returning a row, in which case the columns from the table in which the row had been deleted would be Nulls. I find it hard to see how this would happen, but it's all I can think of to explain the behaviour given that it apparently results from the use of the acCmdDeleteRecord constant of the RunCommand method. There is no suggestion of any other code being called.
_____________________ "Don't write it down until you understand it!" - Richard Feynman
Ken Sheridan,
Cannock, England
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Hi Guys,
Thanks for your responses. I have solved the problem but don't know what really caused it. I started romoving code (too much at one time) and it finally worked, so I'm not sure wihch code caused the problem..
Thanks again,
Phil
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Ahh, yes, an outer join is a possibility I hadn't thought of. I guess we'll never know what the real answer was though.
Was this reply helpful?
Sorry this didn't help.
Great! Thanks for your feedback.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.
How satisfied are you with this reply?
Thanks for your feedback.
Source: https://answers.microsoft.com/en-us/msoffice/forum/all/deleting-last-record-in-a-continuous-form-leaves/a5e7c2bf-1834-4593-bd5e-111abd3ff927
0 Response to "Ms Access Continuous Form Dont Show Last Blank Row"
Postar um comentário