>>>Very key point. Another one is that if an app requires a good number of calculations, queries or lookups, LN is definitely not the way to go. I speak from experience. The powers that be in our IT department wanted to develop a new app in LN, against my advisement, strictly because of its replication. The size and performance of the app was horrendous and thusly I am just about finished a total rewrite in VFP.
>>
>>Well, IMO (FWIW), if LN is already in place one might be justified in using VFP/VB as a front end and LN as a back end. That way you get the best of both worlds...
>
>Have you tried this? If so, how? ODBC? I have, and the performance of retrieving data from a very small, indexed, LN DB was extremely poor.

No, I haven't tried it (and I believe you when you say performance is poor). I've heard about it being done, however. I'm just pointing out that it's a slick solution in search of a problem....