Hmm. Parts of your question don't make sense, but I think I can help you.
LabVIEW has a couple of different ways of talking to GPIB devices, but only one of those ways also works with serial. You can either use the "Traditional GPIB" functions, which _only_ work with GPIB, or you can use the VISA functions, which can work with GPIB, Serial, USB, Ethernet, etc.
So, you should only be using VISA functions. Fortunately, you probably just need to add a few things to get it to work with serial.
Are you starting with the TDS 420 instrument driver from http://ni.com/idnet ? If not, that might make things easier. It doesn't appear to already have serial support, so you'll need to modify it.
My first guess at the problems you are having is that most serial instruments have to have some sort of termination character added to commands when they are sent. So instead of just sending "CURV?", you may have to send "CURV?\n" (where \n is a newline character).
You should read the manual or test your instrument to see what kind of termination character it wants. It's probably either \n or \r (carriage return).
Once you know that, there are a couple of approaches to take. (1) You can edit all of your commands in all of your VIs to add the termination characters. If you only have a few VIs, this isn't too hard. Or, (2) you can tell VISA to automatically add the termination character for you. This is easier.
To do the second option, you can use the VISA Configure Serial Port VI to configure the termination characters.
If you are modifying the instrument driver and want it to continue to work with GPIB, you can put the call to "VISA Configure Serial Port" into a case structure frame that's only called when the interface type is "Serial". You can check this with the VISA property called "Interface Information:Interface Type". Several of our existing instrument drivers do this trick. You could probably search the http://ni.com/idnet for drivers that support GPIB and Serial to see how it's done.
I hope this helps.
Brian