Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP Source Code Converters
Message
From
27/10/2015 01:58:31
 
 
To
26/10/2015 23:04:23
General information
Forum:
Visual FoxPro
Category:
Visual FoxPro and .NET
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 10
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Desktop
Miscellaneous
Thread ID:
01626037
Message ID:
01626479
Views:
81
>You have pretty much proven my point. Converting to "be considered for contracts" means that somehow customers or potential customers are requiring you to do something that makes no sense. As a related example, if an IT dept in a company decides they must convert because VFP is old, the developers doing the work are following instructions to keep their jobs. But the IT people are guilty of wasting company resources and being irresponsible employees.
>
>I never said anything about SQL Server, I would not consider VFP to SQL Server a rewrite.
>
>If a customer is requiring that any app they buy be in .Net, they are also most likely guilty of being irresponsible. There is no business reason for the requirement. You are like the develolpers that the IT dept is forcing to do something. There is no business case, as there is no benefit to the company in requiring an application that functions fine in VFP to be redone in .Net.
>

I think you're missing the point about my referencing SQL Server. In many cases, migrations from VFP to .NET/SQL Server involve a re-architecture effort on the business layer, the database layer, etc. Quite simply, newer features in SQL Server can yield major increases in performance and functionality, and/but are going to require something closer to a re-write. I've seen this as a journeyman consultant many times.

You know that old saying..."you're entitled to your own opinion but not your own facts". I'm sorry, but some of your statements are just too dogmatic. There certainly ARE justified business reasons for moving from a product like VFP to a new development platform - not the least of which is the trends in the industry, the availability of developers, etc. Something might function fine in one product "now", but might not scale well down the road. There are enough factors that we could talk about all day long. Making a generalization that the company is being irresponsible ....well, sometimes there's more to it than that.

Something interesting, your reply to Craig are not consistent with what you've said to me here.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform