Bruce,

I agree. In some cases it's better to just use what you know even if it isn't the best solution. However, using PB/Sybase just doesn't make sense for applications where FoxPro can do a better job with a lot less work. Of course, using just VFP doesn't make sense for systems that really need the capabilities of a server database. Unfortunately, because VFP gets so little notice these days, it's hard to get people to even look into VFP as an option. Even if they realize they don't need a server database they'll probably want to use Access. Yuck!

>The problem I see with PB here is somewhat analogous to the frequent vfp discussions. Many vfpers would like vfp to encompass a lot more than it currently does, rather than use other products with vfp...(I'm not taking any side here, though using one product is generally easier as far as the learning curve, and for legacy purposes...)
>
>What transpires here is that systems people are stuck on PB/Sybase as a solution for just about everything, forcing it on small to medium data-intensive applications, where it isn't the best tool...it's a similar mindset that many of us have, though, I guess...