Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

what do you seggest to immigrate to .net framework? 4

Status
Not open for further replies.

kenwall123

IS-IT--Management
Mar 28, 2012
13
US
Hi everyone
I recently meet someone who programs so many applications with foxpro 7 with large data files and want to immigrate to other platform like .net or java
what solution or solutions do you suggest for this immigration.

thank you Duds
 
Not again...

In the first place, you're not even the VFP programmer. He will need to know his demands and then choose a language fitting his needs.

There is no such thing as a best fit, you just have to rethink with the options you need, eg database, GUI, office integration, platform dependency, webapp? cloud? desktop? and then see what programming platform offers all that. Personal tastes also come into play.

Nobody can answer that but himself. You can get ideas and inspiration from discussion, but there were so many already since the 2007 announcement of VFP being discontinued.

.NET and Java are two candidates for allround IDEs for every need, but you also need to choose a new database, a new language is just a starter, but surely you first would need to decide for which UI you want to go in the future and what platforms you want to support, not only OS platforms, but also device classes.

Then languages supporting that platform often turn out to be JAva and Dotnet, true, but you might also find your freedom with HTML5+Javascript and Open Source tools.

Break it down from your needs, not from a successor language capable to do all VFP can do and more, or you only end up with something you might not be able to get your head around, if you eg never programmed object oriented. You can also do very nice things in a scripting procedural style of programming eg in PHP, which offers you to use it that way or object oriented.

If you have much VFP code you also might want to find a way to integrate it into new development. And this is possible via making your exe callable with parameters or declaring COM servers using the VFP classes, which tehn simply remain VFP. Many programming languages can make use of COM/OLE on Windows, even PHP for Windows via Ole module.

Just to show what you should have found in goolge already. And that was just a first shot on this site, msdn forusm, experts exchange

thread184-1674797
thread184-1671544
thread184-1650272
thread184-1626936
thread184-1664306
thread184-1673283





Bye, Olaf.
 
foxpro 7 with large data files

If the main problem is the large data files, then there's no reason to move completely out of Visual FoxPro. A better bet might be to migrate the back end database, for example to SQL Server or Oracle. That way, he wouldn't have to re-write the front end, which means less work and a better transition for the users.

But as Olaf says, there's no best fit in this situation, and nobody can advise him without knowing a lot more of the background.

With no disrepect to yourself, is there any reason why you are posting this question? Wouldn't it be better if your friend joined the discussion himself?

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips, training, consultancy
 
I agree with both Olaf and Mike.

The answer would be - IT DEPENDS.....

And I also agree that the individual who should be asking this question is the one who needs it first-hand, not another individual.
That first-hand individual knows what they need and can determine the best fit for themselves.

Good Luck,
JRB-Bldr

 
This is sort of directed at Mike / Olaf as 2 of the most prolific contributors here, but also to all. As Olaf said " not again .." , so what is the best dotnet migration plan or more to the point WHY MIGRATE !!

I've dabbled quite a bit in dotNet, replicated most user interfaces dotNet versus VFP, used Sql Server as backend data-base where the client INSISTED. And I have yet to find a case where VFP does not hands-down provide a better development environment for the kind of one-man-show custom development that we all do. Nor have I seen on this site, or elsewhere, one single account of a succesful migration !!

But equally, I am 100% honest with my clients, tell them
1) I am a one-man-show, with the risks that entails
2) VFP will cease official Microsoft support in 2015
3) but VFP and their apps will continue to work for at least 10 years

So, with January 2015 looming large, the question is what we as a developer cummunity can/should do to
4) re-assure our clients
5) counter the inevitable anti-VFP sales-pitches
6) tell the great story that VFP is perfect for the 'cloud'

I would suggest that we form some kind of developer body with a professional brand-name, like " VFP-Insure " or some such , publish directory of members ,web-site etc etc , paid-up subscription to cover this

7) agree source code / other levels of contingency / documentation for our client projects
8) publicise this support body on all our projects
9) agree to support each other's applications in the event of dispute, illness, exit the business etc
10) this support is intended as last-resort, client pays your full per-day rates if he has to invoke.

My belief is that we need something like this, and with it, we could all continue to make a nice income from VFP for another 10 years !!

Sean M
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top