First off we need to clarify what you mean by "Visual" and "Object Oriented".
I will throw out two definitions here:
Visual - a progam and design system that uses diagramming to express algorithms.
Object Oriented - a program and design system that uses controlled methods as the only access path to data.
With these definitions, we realize that the two sets are not exclusive. We then add another definition:
Professional -
# engaged in a profession or engaging in as a profession or means of livelihood; "the professional man or woman possesses distinctive qualifications ...
# a person engaged in one of the learned professions
# an athlete who plays for pay
# engaged in by members of a profession; "professional occupations include medicine and the law and teaching"
# master: an authority qualified to teach apprentices
wordnet.princeton.edu/perl/webwn
Of these definitions, the first, second and fifth apply: as a means of livelihood is the most important.
Now, I would say that Object Oriented programming runs contrary to that goal, but does meet up with the fifth. (you can make more money by billing more time for non-OOP software! But, it isn't very usable by others in the craft).
Visual Programming, though, cannot easily express basic algorithms (you can have a SORT box, but how in blazes do you draw the steps of a quicksort easily? Most descriptions are partly verbal as well.) The MOST visual approach to programming is the old-fashioned "Flow Chart" (dating back over 50 years now). Since "Visual Programming" is so damned difficult, you can certainly make more money at, and thus, I deem it "MORE PROFESSIONAL".
If you haven't figured it out yet, this post is (mostly) tongue in cheek, and is meant to be humorous.
I actually assume that you mean "Visual" in the sense of Microsoft Visual tools, and Object Oriented, well, I am not too sure -- Visual C++, C# and most of the other offerings ARE Object Oriented, so there is no dichotomy.