>>IMO, going to Lianja is a disservice to your customers. Moving from one niche product (VFP) to a product that's even more niche won't help the customer any when they can't find developers to enhance solutions. Too often, we neglect to look at long term affects of our tech choices.
>
>I agree completely.

That is a very valid point...at least right now. If Lianja takes off and there ends up being a bunch of people using it, then sure - but jumping into it at this point seems a tad risky doesn't it? What if it ends up with a small user base? Sure, it might turn out to be huge - but unless yer a fortune teller no way of knowing that right now. Personally I wouldn't take the chance if the project was anything large.

>>
>>>Do you mean Craig's suggestion, or my suggestion (Lianja)?
>>>
>>>Just in case you meant Lianja, it is true that it is aimed at the Access programmers in workgroups or SMB's, in part. That's a huge market, and in fact that's where xBase, and Fox, has its roots.
>>>
>>>Lianja is also, however, highly scalable and clusterable; it is "large numbers of users" multi-user performant. If you need to deploy to 5,000 users hitting a single database, you really want to give this product a look. Lianja has done a good job of making it easy; that doesn't mean the product isn't capable.
>>>
>>>The fancier developer tools I want (e.g., integration with xCase for data design; a Business Rules dictionary tied to metadata) will come with time (as we build them): what's important is that all the objects and hooks we need to do that are either there, or will be provided if we need them.
>>>
>>>Hank