Excel to Foxpro 2.6 1

[Cybermens]

Hello ,

Is there a way to import data from Excel to Foxpro for Dos. 2.6

 

[ravicoder]

Hi

Which version of Excel? I think all later versions of excel are accessible with automation which may not be possible in DOS foxpro.

I maybe wrong but just explore

Regards
Ravi

 

[Cybermens]

I want to import excel data to foxpro for dos .

Are you from India . If you have good knowledge of foxpro can we connect outside this forum .

 

[Gary Sutherland]

Hello ,

Is there a way to import data from Excel to Foxpro for Dos. 2.6

Yes although your options are limited by the versions of Excel supported. Lookup APPEND FROM in the manual. You may find it easier to save from Excel as CSV and import that.

 

[Tore Bleken]

Why don't you take a look at the calendar? It's 2025... DOS is dead, and has been dead for more than 30 years. Upgrade the software to VFP9 before it's too late.

 

[Cybermens]

Why don't you take a look at the calendar? It's 2025... DOS is dead, and has been dead for more than 30 years. Upgrade the software to VFP9 before it's too late.

Technology comes at a price. There are a lot of people who cannot invest again and again.

Foxpro for Dos or for that matter Foxpro itself maybe a dead house but the software which we are using is very much stable and functioning. Building a similar software with similar features will cost a bomb in today's time. Plus implementing and training will be an additional expense, which we cannot afford.
Developing a software completely new wont bring any extra revenue to the organisation which uses this software built with this dead house.

Sometimes upgrades are imposed on us , even when we do not need them. Sometimes upgrades come at a cost which many cannot afford.


Had foxpro been a dead horse , developers would have not considered still developing freedos, dosbox and similar softwares.

Lastly, no one asked your opinion and mind your own business if you do not have a solution.

 

[Cybermens]

Adding further to your comment. Even VFP9 is a dead horse.

Why don't you take a look at the calendar? It's 2025... DOS is dead, and has been dead for more than 30 years. Upgrade the software to VFP9 before it's too late.

 

[Cybermens]

No it's not dead, but it's abandoned by its parents. It will continue to work for ages.

you just said dead and now saying abandoned by its parents. I guess you are crazy. Stop commenting useless and get a purpose in life.

 

[mmerlinn]

Why don't you take a look at the calendar? It's 2025... DOS is dead, and has been dead for more than 30 years. Upgrade the software to VFP9 before it's too late.

Maybe he cannot upgrade.

Or maybe why fix that which is not broken?

I still use FoxPro 2.6b for the Mac because the ONLY VFP for the Mac is VFP 3.0 WHICH IS TOO BUGGY TO USE.

 

[Cybermens]

Maybe he cannot upgrade.

Or maybe why fix that which is not broken?

I still use FoxPro 2.6b for the Mac because the ONLY VFP for the Mac is VFP 3.0 WHICH IS TOO BUGGY TO USE.

See the software that we use in foxpro even after 30 years does the same kind of work for us. What is lacks in modern features like auto email generation , creating dynamic pdf reports. Now previously it was not able to do usb printing and laser printing too. All these we have now over come.

Now thanks to softwares like Dosbox x we are able to run it on windows 11 machines as well.

Now upgrading such a software will cost over 50000 dollars , as quoted by many to ous company. They will make the same software with enhanced features . Most of them most of them offered to make the solution web based which we do not want. Plus investing this amount really wont help our efficiency or profitability as well. Hence the management is against such an upgradation.

Plus upgrading to VFP also makes on sense at this point considering it is also a dead horse. Rather keep if alive in foxpro 2.6 only.

I am 45 years old now. Except to work it 60 years if life permits. Beyond that the next gen of owners of organization can decide if the business survives.

Till then i will keep on finding and figuring out indigenous ways to solve problems. Like 10 years back we figured out a way to generate MYSQL file which we use to export the data on our website.

 

[Tore Bleken]

I am not talking about rewriting the software in another language, I am talking about upgrading it to work in VFP9. I have done several such upgrades, none took more than one week. And I am willing to assist if you want.

 

[Cybermens]

This program comprises of 200 + prg files and more than 15 database .

It is written in foxpro for dos .

Now tell me can it still be converted in 7 days .

 

[Chriss Miller]

VFP9 is still downward compatible with FP 2.6, and Tore is an expert and has already done such conversions. You still think in terms of rewrite, you can take most of your code 1:1. You'll end up seeing your DOS screens in a Windows form, that's mostly what changes.

From the perspecitve of user interface changes though you only have minor visual changes, what remains is the topic of a Windows application being part of a multiple application environment. You might need to think a bit different in hotkeys, though you could still use single letters or function keys and not need to change everything to ALT+ or CTRL+ or SHIFT+ something, but that might not even be an issue, And you get all possibilities of VFP9 and much of Windows, inlcuding all printing capabilities and anything else you lack in FPDOS.

 

[Cybermens]

I don’t think I can do it myself . I need professional help which is affordable .

 

[Tore Bleken]

You have nothing to lose by making a copy of all the relevant files to a new set of folders, and try to run it from VFP9.

Most likely it will run, but look "funny". This funny look is mostly caused by different fonts. If you change _screen.fontname you can try other fonts. VFP9 installs a font called FoxFont which may fix the "funny" look.

If you get errors, fix them one by one.

200+ prg's is "nothing".

By 15 databases, do you mean 15 tables (DBF's) or databases (DBC's)?

Note that I am willing to give it a shot, and offer you up to two hours of testing for free.

 

[Cybermens]

I had tried running the software in foxpro for windows but it never did . So I never tried running the same in visual foxpro .

Let me see

 

[Chriss Miller]

If you change _screen.fontname you can try other fonts. VFP9 installs a font called FoxFont which may fix the "funny" look.

One thing I know is causing seemingly unsolvable trouble is a phenomenon of controls being invisible unless you mouse over where they should be. VFPs Windows themes support is causing this, but you can turn it off globally by setting _Screen.Themes=.f. or call SYS(2700,0) or both.

Since FPDOS or other early Fox versions didn't have Windows Themes support anyway, that's not a loss at all. And what is a drastic glitch can be turned off. The fix was found very soon after VFP9 was released, IIRC even when it was only available as a beta version. So that's an over 20 year old tip, as the VFP9 beta version came out June 2004, the final release version December 2004.

Many people maintained their legacy software in upgraded Fox versions, just didn't incorporated the advances FoxPro made. But since there's a lot of legacy code run under later VFP versions that was discovered early and the workaround was found soon. I don't know who found out that themes support was the culprit, but I remember this fix spread like wildfire, if that off switch wasn't even introduced because the problem revealed itself in the beta phase.