Mostly because of reading this site, I'm trying to move away from Hungarian Notation. Or I guess the improper (system) Hungarian.
I can figure out a better way to name most data types, but I don't know what to do with objects. What would be a good naming convention for objects? I use objRS for recordsets now. Would I just use rs?
I would use customerRecordSet or just customers.
Do you really need to remind yourself that it's an object? Everything is an object, for the most part.
Do you really need to remind yourself that it's a recordset? Once you see yourself treating it like a recordset, it will be pretty clear that it's a recordset.
You tagged your question vb, but your weren't specific as to which vb and the answer here really depends on what version of vb you're working with.
Systems Hungarian notation still makes a lot of sense when you're working with the old vb6 or vba languages. This is because it's a looser type system and you don't get much help on the data types from the IDE. The type information provided by the hungarian prefix is very valuable.
For newer (.Net-based) code, don't use a prefix at all. The .Net Framework likes strongly-typed code and Visual Studio will give you a lot more help when you need it. You just don't have to go around reminding yourself that a variable is an object or an integer or a recordset or anything else; it's immediately apparent in your development environment without any prefix.
Create names that are descriptive of the objects and of your usage of them. The names and the context (not to mention the intellisense) should be enough to remind you of their types as you look at them.
On that note, I feel your pain. I learned VB6 in college and was taught hungarian notation where a variable for a first name would be called strFirst. As I moved over to .NET and C#, I was not quick to let my old habit go even though the accepted standard for C# did not include such notation. I quasi-conformed (or at least, that's what I told myself) by shortening the notation to a single character, so first name would be stored in a variable called sFirst. I told myself I needed that character so I would know what my variable type was. But you know what? It reinforced another bad habit, in that my variable name was not descriptive enough. What is sFirst? First of what? Now, I could have obviously made the variable name more descriptive and kept the hungarian notation, but for me the one bad habit (the notation) went hand-in-hand with the other (abbreviated variable names).
Eventually, and it was probably less than a year ago, I bit the bullet and started writing code the "proper" way. The notation is gone, my names are more descriptive, and (best of all) I have no issue with looking at code and knowing from name/context what type of variable I'm working with and there is also no ambiguity of knowing what the variable refers to. I say let go, you'll not miss it.