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 Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
PROTECT SOURCE CODE
- Thread starter Andy888
- Start date
- Thread starter
- #4
Fluteplr,
Thanks!
I developed this program since 1986. I original use Dbase III. Then changed to foxbase. Since Microsoft bought Foxbase and changed the name to Foxpro. I already used it. it was total over a decade. This high efficient import/distributor and EDI translator software is very valuable to market. If any one interest in my software. May be we can cooperate to market it. Anyway, Thanks you for your information.
Andy
Thanks!
I developed this program since 1986. I original use Dbase III. Then changed to foxbase. Since Microsoft bought Foxbase and changed the name to Foxpro. I already used it. it was total over a decade. This high efficient import/distributor and EDI translator software is very valuable to market. If any one interest in my software. May be we can cooperate to market it. Anyway, Thanks you for your information.
Andy
- Thread starter
- #5
What is wrong with programming with Foxpro 2.6? I still write my programs in 2.6 and they work just fine. I have yet to find anything I need to do for my programs that 2.6 cannot do as opposed to having to go to VFP.
Not all of us can afford to spend more thousands of dollars and hours converting to VFP. I am tired of the VFP parising VFP only because they can afford to. I spent much time and money orgirnally making the 1.02 to 2.0/2.6 jump in retraining time, utilities re-purchasing, etc.
Microsoft bought Foxpro from Fox Software then all our problems began. The free tech support that was part of Fox Software dissappeared, the cost of the software increased, the VFP initial versions were VERY buggy and you had to pay for all support. Then as 3.0, 5.0, and 6.0, and 7.0 were released the costs piled up.
Also, all the aftermarket utility companies seemd to believe we are made of money as well. The magic starting number for most any utility is $300.00 with costs escalating even higher. Look at DevCon, it used to ne $195.00 years ago, now it is well over $1000.00 or more.
I love Foxpro and have been with it since version 1.02. I would be glad to go to VFP 6.0 (which I own, by the way), but since I have no income from it and program mainly for charitable or non-profit orgranizations which I belong to mainly to make them more organized, I receive no income for it thus cannot afford the costly training afforded by the various companies or the utilities available. Plu the fact that many of us figure that eventually Microsoft will phase out Foxpro by integrating VFP, VB, and Access into one software! Then where will us staunch Fox supporters be?
Even the utilities I own from 2.6 version are extremely costly for upgrades (usually more than I paid for the initial versions). Sure they are affordable for the corporates that pay for everything but what about the 'littlr guy' and hobby programmers?
I have some utilities I purchased that never worked correctly and once they fixed them they wanted me to pay again for them! I also have several I purchased that were buggy like FoxWeb and now that it apparently works correctly they 'lost' my 'Registration' and tell me I have to buy it again (I was one of the VERY FIRST purchasers of it). Not to mention all the money I have spent on Foxpro tech books. Notice how the prices have doubled and tripled for them over the last ten years? Here in Las Vegas, Nv bookstore won't even cary them. The last I checked with all the major bookstores here only one has one obsolete VFP book on the shelf but they all have hundreds of books on VB and Access!
So please do not be quick to criticize those still standing by 2.6. It is very stable and works just fine!
Not all of us can afford to spend more thousands of dollars and hours converting to VFP. I am tired of the VFP parising VFP only because they can afford to. I spent much time and money orgirnally making the 1.02 to 2.0/2.6 jump in retraining time, utilities re-purchasing, etc.
Microsoft bought Foxpro from Fox Software then all our problems began. The free tech support that was part of Fox Software dissappeared, the cost of the software increased, the VFP initial versions were VERY buggy and you had to pay for all support. Then as 3.0, 5.0, and 6.0, and 7.0 were released the costs piled up.
Also, all the aftermarket utility companies seemd to believe we are made of money as well. The magic starting number for most any utility is $300.00 with costs escalating even higher. Look at DevCon, it used to ne $195.00 years ago, now it is well over $1000.00 or more.
I love Foxpro and have been with it since version 1.02. I would be glad to go to VFP 6.0 (which I own, by the way), but since I have no income from it and program mainly for charitable or non-profit orgranizations which I belong to mainly to make them more organized, I receive no income for it thus cannot afford the costly training afforded by the various companies or the utilities available. Plu the fact that many of us figure that eventually Microsoft will phase out Foxpro by integrating VFP, VB, and Access into one software! Then where will us staunch Fox supporters be?
Even the utilities I own from 2.6 version are extremely costly for upgrades (usually more than I paid for the initial versions). Sure they are affordable for the corporates that pay for everything but what about the 'littlr guy' and hobby programmers?
I have some utilities I purchased that never worked correctly and once they fixed them they wanted me to pay again for them! I also have several I purchased that were buggy like FoxWeb and now that it apparently works correctly they 'lost' my 'Registration' and tell me I have to buy it again (I was one of the VERY FIRST purchasers of it). Not to mention all the money I have spent on Foxpro tech books. Notice how the prices have doubled and tripled for them over the last ten years? Here in Las Vegas, Nv bookstore won't even cary them. The last I checked with all the major bookstores here only one has one obsolete VFP book on the shelf but they all have hundreds of books on VB and Access!
So please do not be quick to criticize those still standing by 2.6. It is very stable and works just fine!
I keep seeing the question pop up in this forum along the lines of 'Why are you still using FoxPro Ver. ...?'
Ever heard the line?:
"If it ain't broke, don't fix it."
There are a lot of useful apps I have developed/maintained using Fox DOS and Fox Win. In fact, I am still using these products because I can't find reliable 32 bit software interfaces for VFP for the type of apps I develope. There is not always a good reason or justification to "upgrade" to VFP. Sure, there are apps that must be developed in VFP, but rewriting an app just for the sake of rewriting is kind of like reinventing the wheel, no?
I think pre-VFP Fox is only considered obsolete by Microsoft, because they don't want to bother staffing a crew to support it. As long as I have a need for it, I will continue using it. Just like I will continue driving the '47 Plymouth as long as I can keep it running.
Dave S.
Ever heard the line?:
"If it ain't broke, don't fix it."
There are a lot of useful apps I have developed/maintained using Fox DOS and Fox Win. In fact, I am still using these products because I can't find reliable 32 bit software interfaces for VFP for the type of apps I develope. There is not always a good reason or justification to "upgrade" to VFP. Sure, there are apps that must be developed in VFP, but rewriting an app just for the sake of rewriting is kind of like reinventing the wheel, no?
I think pre-VFP Fox is only considered obsolete by Microsoft, because they don't want to bother staffing a crew to support it. As long as I have a need for it, I will continue using it. Just like I will continue driving the '47 Plymouth as long as I can keep it running.
Dave S.
Damn, we have over 40 sites... running foxpro 2.5 for dos
point of sale system, company's sales are 240 million or so
would have.... 500-600 users
all of head offices marketing/pricebook databases are all
foxpro 2.6 for windows... some 2.5 for dos....
everything has been developed inhouse... over 9 years...
I personally love fox... is soo easy to write in... but I may have been doing it too long (7 years now)
Or it dept, is made up of 5 people, 2 programmers, one network guru, it manager and our office lady (most important person)....
Honestly for our setup... it wouldn't be worth... moving to another system.... would cost way too much... just in hardware alone (some sites have 9 year old hardware... 386sx 25 with 4 megs)...
Zim
point of sale system, company's sales are 240 million or so
would have.... 500-600 users
all of head offices marketing/pricebook databases are all
foxpro 2.6 for windows... some 2.5 for dos....
everything has been developed inhouse... over 9 years...
I personally love fox... is soo easy to write in... but I may have been doing it too long (7 years now)
Or it dept, is made up of 5 people, 2 programmers, one network guru, it manager and our office lady (most important person)....
Honestly for our setup... it wouldn't be worth... moving to another system.... would cost way too much... just in hardware alone (some sites have 9 year old hardware... 386sx 25 with 4 megs)...
Zim
I have no problem with people who don't upgrade from FPD, as long as they don't complain about how it "doesn't work (right)" on thier new W2K box. If you (or your users) can afford to upgrade hardware or OSs, then you CAN afford to upgrade your development environment and those applications.
'Nuff said,
Rick
'Nuff said,
Rick
infinitelo
Programmer
- Mar 7, 2001
- 319
here is a good one a while back one of our pc's got hit by lighting, windows would not start afterword. i used a floppy to boot the computer and ran my dos foxpro executable and was able to save the data on the hard drive
after the tech said it was toast and the hours of work was lost.
never forget dos runs then windows.
after the tech said it was toast and the hours of work was lost.
never forget dos runs then windows.
- Status
Similar threads