Thanks for your reply, Brandon. Your advice is quite helpful. Yes, RPG is still used. We are still using it. As languages go, it makes COBOL look cool. If there is a worst thing you can say about a language I can't image it.
LINQ has look particularly interesting to me. I can see a number of uses for it to make processing more straight-forward. I have wondered if there is a performance hit for using it though. Much of the application is either users entering or looking up data. Even a few seconds delay for those tasks can make for a frustrating experience. I expect I will definitely use LINQ for batch processing, but I am curious about how well it performs when used for time critical operations. I take it forom your experiences that you have not had any significant performace issues? The same is true to the Entity Framework. If the overhead is minimal, I'm all for it. If the overhead is not minimal, then I may have to regulate using it only for specific tasks. In particular, I need to know if the Entity Framework is faster or slower than typed DataSets, which is as slow as I'm willing go. Once again, I take it you have not had any performance problems using the Entity Framework. I'm still reading up on WCF. Based on what you said about it being awsome I shall read faster. Thanks again for your feedback. I'll speed up my studying of LINQ as you suggests. - R.B. Davidson On Feb 3, 5:47 pm, Brandon Betances <[email protected]> wrote: > Great to have you hear, Brother. First off, I haven't seen RPG in YEARS. > Believe it or not, some people still use it. > > Your concerns are understood. I would read up on LINQ extremely fast, > because it is a great technology that I use as much as I smoke cigarettes > (bad analogy there). The ADO.NET Entity Framework, and LINQing to it, are > the way to go when you want to access data. > > WCF is an awesome technology that promises to turn the Web Service work > upside down. > > WPF is cool, but I don't use it yet, so I cant comment. > > Same for WF. > > LINQ is my first stop for you, though.
