Yes Jayanta, it did work.
Joe, between the two feature classes, I was able to copy from one to the other but not the opposite way around.
Basically, I had a table of addresses (We'll call it Table A) that I had X & Y values for that I easily generated 500+ points from. The attributes obviously remained the same. I had a second table of roughly 30 addresses (we'll call it Table B) that had no X & Y values. So I geocoded them and took care of the unmatched/tied addresses to get as many accurate points as I could. That process of course, generated extra fields. The table for this one also had a couple more fields than Table A prior to the geocoding.
My ultimate goal was simply to get all of the resulting points from both feature class A (from Table A) and feature class B (From Table B) into one feature class. It wasn't a concern if I ended up with all fields of both, included in the final output because I was just going to be using the points for a density map.
Initially, I tried to copy/paste from feature class B to feature class A. It didn't like that. So for grins, I tried to copy the opposite way around. I was able to do that successfully. Basically, all of the fields I had from feature class B, are empty for the features I copied from feature class A in the output. I'm still trying to figure out why it worked one way but not the other.
Thank you both for your replies.