The Short answer:
Procedural Basic code just flows from first line of code to last line executing in order. You can alter the flow with obvious things like a Main Loop which calls various subroutines, until at which time the user does something that ends the code (like dies in a game or hits esc to break to program)
Object Oriented is just that....everything is an object (instantiated from the Class) that can contain methods, properties, and events-all of which are hinged on (watched over by) the operating system (win) which is actually a timer-based polling system (Like an infinite main loop that you don't tinker with). Properties are properties of the object, like if the Object was a book, for example, a property could be PageCount, PageColor, TextFont, etc etc. A method is a sub or function contained in the Object which goes and does something like MyBook.FetchPage(ByVal PageNumber as Integer)As String. The object also raises Events (detected by os) which triggers other functions or subs to run, or throws an Exception (object) when an error occurs. An Event is most commonly triggered by the user interacting with the program like pressing keys or clicking the mouse.
In short Procedural and OO are closely related logic and coding wise but differ greatly in how and why things execute as they do - actually OO is just a bunch of little blocks of procedural code just waiting to be called with no predetermined order of how things will happen.
The differences are vast and I probably shouldn't have gotten started trying to explain this as to do it correctly would take me days or weeks - LOL.
I prefer to code in an OOPL but I really like DBP too!
sorry for the short lame explanation-just scratching the surface...
-RUST-