FoxPro Agony

We just finished defending our database application project yesterday morning. It's a good thing that our CS 312 teacher extended the deadline because the RC Marketing Database System is relatively complex. We have been excruciatingly hoping for the friggin' FoxPro to cooperate with what we want it to do. We have been revising codes and layout several times that we cannot even keep track of a numbering system to label the versions of the application.

The ADD ORDER form, in particular, is madness! Error messages came out from everywhere! I have been making excuses like "It'll only work in our computers," and "FoxPro is stupid!" I cannot have the mood to enjoy recounting the chronicles of our attempts to bend FoxPro to our will, except the climax.

On the eve of our defense, the "File must be opened exclusively" devil came back like a nightmare coming true. We were frantically trying out solutions like browsing tables, modifying the data environment, and running the form several times. It was working in our home PC's. Why not in the office computer?! I remember myself stupidly reasoning out, "Baka ayaw n'ya sa computer dito sa office, sa bahay lang..." We were so desperate.

Then we realized that our home computers have something that the computer in front of us didn't have. Administrator account privileges! So we restarted the PC, typed in 'administrator' in the user box, opened the FoxPro project file, pressed the 'Run' button, tested the ADD ORDER form, then here I am typing a post about how finally defending this despicable application is a breath of fresh air!

After all that, our group buried FoxPro several feet below the earth and vowed never to dig it out.

May it never rise to haunt us again...