Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VB Interop Toolkit
Message
From
28/03/2011 16:57:21
Jarid Griesel
The Innovix Technology Group (Pty) Ltd
Johannesburg, South Africa
 
 
To
28/03/2011 10:54:22
Joel Leach
Memorial Business Systems, Inc.
Tennessee, United States
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Environment versions
Visual FoxPro:
VFP 9 SP1
OS:
Windows 7
Network:
Windows 2008 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01505061
Message ID:
01505286
Views:
69
Our application is extensive and complex and has lots of UI.
VFP's UI is dated and "simplistic" although blazingly fast compared to Winforms.
We also need more powerfull data visualisation / viewing / drill down capabilities.
.Net offers more compeling UI controls that facilitate data analysis in modern paradigms.
There are hardly any vendors are doing great ActiveX controls that VFP compatible.

Also we are concerned about the longevity of the VFP UI controls in relation to future versions of Windows.
Remember VFP's UI control's are not Native Windows controls like in VB6 but are a graphical contrivance native to VFP.
We are concerned that VFP's UI may "break" under future versions of Windows wether it be Windows 8 or Windows 9 but that day is sure to come and we do not want to be faced with a major rewrtie at short notice.
Also VFP will fall behinf in SQL Server compatibilty over time. Etc , etc, etc.

For us and in relation to our application, .Net offers us modern and more powerfull UI capabilities and then to be on a tech platform that will be compatible with future Windows versions.

Put another way, had MS not abandoned VFP many years ago, this thread would never have been started.

Our application is such that it is best suited to a Windows Client architecture and WinForms, although "dead ended", is a good fit and allows for very complex UI, maybe not as glassy as WPF or Silverlight.



> What advantage does WinForms have over VFP? It does get you to .NET, but for me, I need a compelling reason to switch, not make a lateral move. WPF and Silverlight have more to offer. Of course, everyone's requirements are different, but something to think about.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform