[comp.databases] dbase hell at BSU

tiddly@bsu-cs.bsu.edu (Tad K. Lynch) (04/26/89)

Well, Mike wasn't kidding when he said 7,000 lines of code,
my team did a project, and we were forced to use dbaseIII+,    
and when all was said and done, we ended up with 11,000 lines
of code.  

After getting everything together, we tried to compile with
QuickSilver, and it compiled great, the only errors were in 
4 files, and they had to do with an endif expecting enddo.
So, anyhow, after it compiled, we were getting an data type
mismatch error during the run that we don't get when we
run it through dBase.  Any suggestions out there?  We don't
necessarily have to have it compiled, but it would be nice 
to turn in a 178K compiled version of the program as opposed
to having to turn two disks over to them, and then making
them have to run it through dBase all the time.

As far as editors go...I like vi for the PC, thats what
a teammate and I used all semester, another member used
sidekick, and the other used PT, a mouse editor.  I was
using PT near the end of the semester, and I really liked
it.  It allows the user to edit more than one file at once,
and allows you to paste between files, ain't that great!!!
It helped me immensly during the documentation of the 
files, and it was a pain, cause we had 70 modules.

If ya'll want, you can e-mail me responses about the compiled
version problem, I'll probably be posting horror stories
sometime soon, Same Bat-time, Same Bat-channel!!

Tad K. Lynch