I can’t tell you anything sensible in VB land sorry (and barely in C# ) but here’s how I would approach this.
Figure out how to write text to the display. Create a string and put that somewhere on your OLED display. Then change the string and update the display. This teaches you how to get the output portion working.
Figure out how to read strings from a file on SD card. On your SD card, just have a file that has lines of text like “Surname: Smith”. Then output those lines to your (working) OLED code. This teaches you how to get the SD card reading working.
Figure out how to get and use user interaction. Make sure you have enough concepts like “next” and “previous” because you’re going to need that in your scenario. Do you have hardware to do this like push buttons - and how are you going to react to those button presses.
Figure out how to parse text. Figure out how when you read a line that says “Tom Smith” and “Tom Jones-Smith” how to get the component parts. Then write the component parts to the OLED. This relies on the working SD card code, and the working OLED code.
Then think about stranger cases, like “Tom De Angeles” (and as many other things you can think of). Think about how you might use typical CSV delimiters like double-quotes around strings and commas to separate values. At this stage you will probably throw out your original parse code and make something more robust that handles CSV format and decide this is a good idea to use from now on Again, test it by writing to the OLED.
Then include multiple lines of data into your file and iterate through them, when directed via user interaction that you got working earlier.
Each time you build on a concept you’ve explored and succeeded with. Each one is discrete enough to be less daunting, and you’ll find examples on the net for this (although VB examples in netmf will be scarce, you are among the minority doing this - but there are vb examples on the codeshare here)
good luck - and when you hit a specific question, not just a big open ended generic one like this, come back and ask. You’ll find we’re all interested in helping you fish, but not in tying the fish to your line first up, so you’ll get maximum help (and maximum learning too) when you’ve tried and shown us how you’ve hit a problem, rather than just asking for documented code