Hey Z, just to clarify some points.
First off, it's not so much that programming in any language is any more difficult that any other language. The bulk of the work is in defining the problem and then being able to express the solution. Your choice of language is then simple a matter of knowing which syntax to use.
The major difference, in the case of DB/DBP and VB is the functionality build into the runtimes of the languages. For example, VB leverages Windows controls and the event-based programming style.
Games programming, on the otherhand is largely the domain of timers and render loops. Because we don't want to mess with all the dirty internals of DirectX (we leave that to Lee and Mike), we can stand on top of the DB/DBPro runtimes to build, at almost no cost, 3D and 2D worlds for our games to exist in.
Is it easier? Well, if you're writing a game it is. If you're building a database app, you're likely best to use another language.
How is it easier? Largely, it is because the game engine and all of the control over the DirectX libraries are handled for you. This means you don't have to worry about OO code, programming against interfaces, complex DirectX types and the intrinsics of tying all the DirectX features together. You get them all at your disposal in DBP by simply clicking "new project."
Do you really have to write all that code? You bet. This isn't a RAD tool as in the likes of VB. There is no interface to drag-and-drop a video game together (not a generic one, anyways).
Is it hard to learn? hrm...well, the question more becomes "Do you really want to program video games?" This isn't rocket science to pick up, but without a ton of experience some of the more advanced topics will be harder to understand. A good working knowledge of the mechanics of a game helps, and understanding the process of development helps A LOT!
-= i only do what my rice krispies tell me to do =-
