>I've used PB from 3.0a to 5.0. Most of its power is in the DataWindow (dw). Concentrate your efforts on it. As of 5.0 it still can't be inherited, because it is bound to specific data, but it is an awesome tool. You will find the GUI very easy to learn, since you already have VFP5 experience (I'm assuming. The only trouble will come as you learn to analyze a situation to determine what and how many 'pebbles' (*.pbl - PowerBuilder Libraries), and other resources you'll need. PBL's are sorta like DBCs. PB is even more graphical than VFP, it doesn't have a command box, and you can access data only through an app or through data managers tools that come with the package. The DeskTop developers version comes with SQL Anywhere, which is a really smooth backend, which means that all of your data connections are ODBC. And, like VFP, you have to watch out for the phantom record! A generally adopted rule is to keep your executable as small as possible, usually just a 25Kb stub, by
>allocating all of your tables and proceedures to pbls and resource files, which then allow for easy upgrading or patching.
>Good Luck

Thanks Jerry for your concise and quite invaluable advice. Ive just landed a contract this morning where they will train me in VB and PB, or let me train myself in their time :)This is exactly what I needed to know. Ive just forwarded your advice to 2 other friends you are currently moving from 2.6/5 to pb hopefully now they will 'get the picture' of what the UT is all about
Regards
Malcolm