Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Best way to handle cursors..?
Message
 
To
15/01/2013 10:07:21
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 9.0
OS:
Windows 7
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Desktop
Miscellaneous
Thread ID:
01562212
Message ID:
01562603
Views:
33
>That's a sure way to have a bad app in .Net. Perfomance and maintenance will suffer. What's behind the scenes should be optimized for the language/platform.

Well Dorris, there you go. Re-engineer your application from scratch and you will have a "good app in .net. Performance and maintenance won't suffer". Never mind what you really need and what your users expect, and your clients are ready to pay.

>Most VFP apps are designed to use cursors (tables and views, basically the same thing).

A cursor in VFP is a normalized object in memory that can be sql'd (read joined) together with actual tables in the DB. I still want to hear the argument that this was a bad idea.

>Thousands of apps access .dbf files directly and use SEEK, LOCATE, etc and don't have a single SQL statement. .Net has an entirely different approach to data.

Craig, there is nothing wrong with having a new approach and electric cars are the future. But does that mean we should as of tomorrow close down all the gas stations?

I know I know, I am beating dead horses here. But I was really surprised how much effort has gone into learning VB.Net (from VFP), given that so much effort has been made to make it a decent programming environment. That being said, I'm glad I did the effort.

If things have the tendency to go your way, do not worry. It won't last. Jules Renard.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform