question para sa mga veteran programmers

[cold_fusion]

---

Visual Foxpro is still supported by Microsoft and is still included in their Visual Studio Package.

Also Windows can always run already compiled programs.
You maybe will have problems if you want to change or add new features of your system and the no new compiler is available.
Pero kung wala kay usbon, why fix it if ain't broke.

[kibotizer]

see the proposed system added benefits if you are going to replace it from your old system, meaning compare and check if the proposal is very beneficial and is very different and more systematized than the old one... then, analyze if the benefit is ideal for the corresponding cost... then, check if the organization can afford to have it... if found FALSE at least one of three then deny the proposal and stick to the current system since no problem has been found... actually there are many factors that you must have to consider and these are just some...

mag-COST BENEFIT AND ANALYSIS and COST AVOIDANCE pod ka ani bai

yeah! bling bling men...abz'

[Jansian]

For me situation lang ako ikahatag sa imo bro, its up to you to decide. My situation is sa pagkakaron ok pa ang inyo system mainly because naa pay makamaintain sa foxpro system ninyo and to think hapit na magnihit ang mugamit ani na language. Let us say 5-10 years from now buhi pa inyo company or successfully nigrow inyo company to a better company than b4 and by trend wla ta mahimo if ang inyo programmer at present would look for greener pastures so for sure mangita mo ug programmer na kabalo ug foxpro in which at present namroblema na gani mo ug kinsa ang ipuli na kabalo mumaintain sa inyo system. Let us say ok ang system manageable cya basically because ang system ninyo na foxpro karon nifit sa process ninyo daily but what if nidako ang inyo company and gakinahanglan ug additional specs, so it could be mupahimo mo ug system na mufit sa new specs ninyo or worst iupgrade inyo current system. I've migrated data from diff. databases including foxpro and kabalo ko unsay structure anang foxpro which is very complicated in data migration process especially kung dako na ang inyo data. Nakasulay ko ug migrate ug data na ang system was developed sa clipper and ang data is .dbf it is a banking system na to think crucial kaayo na sa migration process wherein mistakes are not allowed sa migration kuyaw na makiha ang programmer for negligence, it could also happen sa inyo company. If ever mag-upgrade mo do it earlier pero if dli mo sure na mudako ang inyo company or dli mo sure unsay changes sa inyo company probably magpabuhat nlang jud mo ug customized na system that would fit sa inyong process and both cost a lot of money. Sak2 na magsurvey usa ka like doing the cost and benefits or pros and cons so it could help the company decide on that matter. Bro, trust me magkadugay ang system ninyo the more na magkamahal ang maintainance. Try to think of cobol programmers now a days. Mostly sa mga big companies na dli makabiya sa ilang mainframe na cobol would pay their programmers @ high price. Why is that? Coz lisud ipangita ug cobol programmers nowadays and the company couldn't risk their income just by leaving the old mainframe behind.

[chewbacca83]

good point Jansian. will keep it in mind.. mao bitaw nagthink sad ko nga i.upgrade amo system using a newer programing language. and your right ang pinakahasul gyud ani kay ang data migration.. mao bitaw hesistant sad ko gamay mu.ilis kay for sure i dont think mudako pani amo company.. kay hasul na gani nga di mi dako, unsa na kaha ko maabot mi ug 1000... hehehe

another question for you guys out there, which program is suitable to make a system? hmm.. unsa may factors nga angay ninyo mahibaw for you guys to answer that question?

thanks gyud kaau sa mga nireply ha its been really informative on my part.. dammit.. i should have listened in school! hahahahah

[maddox]

Java EE or Microsoft .Net

Depende sa budget plan sa inyo company. Microsoft is not free and in fact is expensive. Java is free w/ a lot of open-source tools supporting.

But with Microsoft naa gyud support nga klaro gikan sad sa ila. With Java, ang support gikan sa community. Ok man sad but medyo dili ingana ka-pas-pas ang response compared sa MS.

But again, i-consider nimo nga ang usa libre and usa dili. So depende sa inyo budget.

[digitalsuperman]

as they say, if it aint broke, don't fix it.

also, although Foxpro isn't packaged with Visual Studio recently such as VS 2003 to 2008 but still MS has been good enough to keep it up to par with its other technologies such as C# 2.0 and VB 9 .. Fox Pro 9.0 is quite awesome on its own.. do some google perhaps you might find something interesting..

[psyd_1]

as they say, if it aint broke, don't fix it.

sakto..maypa invest nalang into other techs na makabenefit sa inyo company, instead of spending lotsa money para sa new architecture na no need na man ang migration kay okay pa man ang inyong existing...

[digitalsuperman]

Java EE or Microsoft .Net

Depende sa budget plan sa inyo company. Microsoft is not free and in fact is expensive. Java is free w/ a lot of open-source tools supporting.

But with Microsoft naa gyud support nga klaro gikan sad sa ila. With Java, ang support gikan sa community. Ok man sad but medyo dili ingana ka-pas-pas ang response compared sa MS.

But again, i-consider nimo nga ang usa libre and usa dili. So depende sa inyo budget.

actually .Net is free.. they have express editions for create desktop applications. for your presentaion or UI layer you have VB, C#, C++ and J# Express Editions... and for your data layer, you can use SQL Server 2005 Express Edtion also.. and in those express editions you can develop enterprise level applications...free forever.. on that note when the express editions started, it wasn't meant to be free forever..if i'm not mistaken it was only for free for about a year..that was their decision early this year, but on later this year, MS changed its mind and kept it free forever..i've read that on a member of the VB Development Team Blogs on MSDN.

when it comes to community support, .Net isn't behind.. you can search through all MSDN Blogs of the C#, VB,C++ and J# Development Team members blog and in there you can post any questions you might come up with and they'd be happy to answer.. also, on the MSDN Forums, you can post from beginners to advance questions so that other developers can interact with you... so you have either MS Support via the developers blog or the community support via MSDN Forums..

[uzumaki]

at the very least visual na cya so its way better compared to DOS program:

Here's my point:

Payroll System: If all system was done thru vsfoxpro. i bet the timekeeping module is somewhat erouneous. Reporting module especially in generating payslip is not that detailed i supposed.

Inventory System: generating reports from stock card, etc.,, are not that easy to produce unlike using vb & crystal report.

...anyway if the system is serving its purpose then by all means maintain nalang...it would be less hassle in your part

[CmdrAdobo]

If it's not broken, dont fix it.