what is largest foxpro application you know of

[113983]

We have a large foxpro app and are considering converting it in the future and would like to know what others have done. Probably convert to C Sharp and MS SQL. Any suggestions

 

[JRB-Bldr]

When you say "What is largest foxpro application you know of" I'd recommend that you clarify.

Largest how?
* Largest single data table?
* Largest number of total data tables?
* Largest number of users?
* Largest code line count?
* etc.

If you are converting an old Foxpro application vs a Visual Foxpro application then, without a doubt, the easiest conversion route would be to take the FP application into VFP. Most of the code can stay intact and it will run.

Caveat - If you wanted to move it up to a 21st century GUI, then the FP Screens would need to be re-developed into VFP Forms.

If you merely want a LARGE data table, then a VFP application can work very well with a MS SQL Server back-end.

Perhaps with better clarification, we can come up with better responses.

Good Luck,
JRB-Bldr

 

[Mike Lewis]

I'm sure that many of the folk here have moved a Foxpro app to a different back end -- SQL Server, Oracle, or something similar.

But that's not the same as converting to the likes of C#. A FoxPro app with a different back end is still a FoxPro app. Rewriting the app in a different language is another matter.

So, what exactly are you asking? And why do you need to know which is the larges app I know of?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[113983]

sorry - we are in VFP 9 but realize that MS is not going to be doing any improvements to VFP so are looking to future. By largest, I meant in number of screens, exes or apps, reports etc.

Probably we will be re-writing in another language (C sharp?) but still should be able to use a lot of the select-SQL statements we have developed for VFP.

 

[113983]

Hi Mike - mostly asking out of curiosity but also if any have gone thru the process

 

[craigber]

The largest FoxPro app has generally been considered the Euro Tunnel (Chunnel). You can read about it here

http://my.advisor.com/Articles.nsf/aid/MATIV02

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com/blog

 

[SnyAc]

I'm planning on supporting and using VFP for at least another 10 yrs... don't know why people seem to want to abandon it.

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Mike Lewis]

I'm planning on supporting and using VFP for at least another 10 yrs... don't know why people seem to want to abandon it.

Well said, Andy.

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[GriffMG]

I live in hope too - although M$ don't seem to be making it any easier for us to do so... 64bit environment with 32bit OLEDB is a bit of a pain.

Regards

Griff
Keep [Smile]ing

There are 10 kinds of people in the world, those who understand binary and those who don't.

 

[craigber]

There could be a number of reasons to move away from VFP:

- Your client base doesn't want it
- You need to do something that is impossible or difficult to do in VFP
- You can't find VFP devs in your area and telecommuiting is not an option
- Your management tells you to move to something else

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com/blog

 

[113983]

I have to agree and we are not looking forward to the day they (MS) stops supporting it. We have app of over 200 exes, 750,000 lines of code and are not looking forward to moving - but 64 bit will someday become 128 bit and .... when is the correct time to move forward!?

We love VFP and can blow the pants of competitors with its speed.

 

[Olaf Doschke]

when is the correct time to move forward?

You just answered that yourself: As long as your VFP Apps performance or feature richness is superior, no need to change. The first step in changing would rather be learning the new technologies. And migrating a big app is in no way a good case to learn new technology.

To answer your original question: Half a year ago we rolled out a reimplementation of a VFP9 app, reimplemented in VFP9 with the move to an SQL-Server backend, a database redesign, some new features, mainly implementing the app in a certain framework not only for the SQL Server support and incorporating a treeview into redesigned forms (which was an extension to the framework). I had to learn a lot about SQL Server and that framework (it's a spin-off of Mere Mortals not publicly available). Migration time was about 15 months.

This app is having about 200-300 users at our customer and is for research and development of cosmetic formulas. I'd call it an enterprise app. The database was at 8 GB before moving to SQL Server and now is several times bigger (this doesn't compare well as it also includes transaction and reserved space, which indeed is unused).

Looking back I could have used some time on new technologies with a smaller job first, besides that moving data only first was a good decision, as the data is the most value of such an application and is now accessible to more smaller apps of the IT landscape already. Changing the programming language of the app itself wouldnt have that much of an advantage. A more modern look is not what the researcher/developer needs. Data entry and data mining apps are not games.

Bye, Olaf.

 

[Mike Lewis]

113983,

Don't forget that whatever platform you move to, you will eventually have the same issue of a limited support period.

By the time you've done the conversion and run the new app for a couple of years, your new language and database will start to look out of date. The vendor (or a competitor) will have come up with something better. Your management will want to know why you are using "old" technology, and you'll be faced with the same agonising decisions all over again.

That doesn't mean that you should never upgrade and move forward, but don't expect such a move to be the answer to the problem of the finite support period.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro tips, advice, training, consultancy
Custom software for your business

 

[craigber]

113983?

64 bit. 128 bit. WHen is the right time to move? There will always be something bigger and better coming along. If you keep waiting for it, you'll never move.

Craig Berntson
MCSD, Visual FoxPro MVP,

http://www.craigberntson.com/blog

 

[113983]

Thanks everyone - and thanks for the heads up Olaf - a good idea to start small and learn the technology before jumping in. We do have one application that is only one exe and probably only about 20 scx's so would be good place to start. Thanks again. You guys always have good answers!

 

[ronald777]

I'm planning on supporting and using VFP for at least another 10 yrs... don't know why people seem to want to abandon it.

ur right Andy