Thats pretty much what i did here (with add and remove, and then a send to DB button too)!!!!

http://img151.imageshack.us/my.php?image=trsufxc4.jpg

With regards to my suggestions for the form, I must admit that I was directing these more to the ‘Naming Userform Controls’ issue than the ‘Pseudo Scroll’ posting.

I will resolve to ‘must try harder’ in future. Christmas Greetings to all.

For saving and applying, I think I will go with a form-wide Save button and Apply button. So records are changed as the user types, but they are not saved until the user Saves or Applies. In code, I’m thinking I’ll create two collections instead of one: a working collection and a permanent collection. The working collection will change as the form changes. The permanent collection will be passed out of the form and back to the business logic layer. The working collection will overwrite the permanent collection whenever the user clicks Save or Apply. If Cancel is clicked, the original, unchanged permanent collection will be passed out. Am I missing any traps here?

I must admit to being slightly confused by the need for last, next, prev and end controls…

Now Andrew, I know you’ve visited this blog a time or two. I would never make a userform that wasn’t keyboard friendly. If only to avoid the public scrutiny. I’ve done some data entry in my day and I always appreciate a keyboard shortcut.

Re CRecord: Andy is right. I meant to post a link to the newly updated Excel file, which I now have done.

CRecord is a class module which you need to create.
This should be enough to get the code working.

Public Name as Variant
Public Department as Variant
Public Current as Boolean

Whilst I note your suggestion, looking at the current screenshot, the current entry is duplicated in both the Controls and the Listbox, which is not as I had intended. It seems to me from a users point of view that if it has been added to the list, it shouldn’t be shown in the control entry section and vice versa.

An Autoupdate function on the Chckbox is not feasible given that no action may be needed on a new entry, and an auto posting on either name and department if they both needed changing at the same time, could lead to an autoposting of an entry you didn’t want !

I must admit to being slightly confused by the need for last, next, prev and end controls when a simple click on the offending entry could remove it from the list and bring it back into the controls for editing, re-enter or delete/clear with appropriate buttons.

It really depends on what you are trying to achieve at the end of the day, but with the method shown, at what stage are all the entries cleared ready for the next entry.

PS Excel 2000 does not support ‘Dim clsRecord As CRecord’ which version does ?

Add button
Delete button
Sort by clicking on column header labels (make them look like buttons, sort ascending on first click, descending on second)
Up/Down buttons for manual sorting (useful for some uses)
Better alignment of header labels and controls with listbox columns

For saving, since it writes to an array, you can give the user two buttons:

Cancel: close without saving to sheet
Apply and Close: saves array to sheet and closes form

Optional third button:

Apply: Save array to sheet now, leave form open for further revision
(these changes are not undo-able using Cancel)