>> >> >> >>>It's a great way to share information of any sort. It replicates quickly and overall LN is pretty powerful (especially when tied to Domino, the web server application) and is easy to administer. However, the client is getting large (feature creep) and, unless one needs a corporate messaging solution, I wouldn't recommend deploying it just for it's database/replication capabilities. >> >>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...
Actually, IMHO, the inverse would probably be better if it was functionally feasible. I believe I recall an article in Notes Advisor about a LN frontend / Relational Database backend. Just a thought, I've never actually tried this and don't want to either :-)
Colin Magee Team Leader, Systems Development Metroland Media Group Ltd. Mississauga, Ontario, Canada
