[palmer]

Throwing more money at the problem won't solve it. [This latest glitch] was a technical issue and we just had to keep troubleshooting until we found it. And no, we're not going to invite a bunch of strangers in to get their hands on our secure systems. John has been programming since he was 14 and he's pushing 40 now. He built these systems and he's an expert in them.

I can relate having programmed for about 35 years, always build from scratch, build it to last, not to throw away and start over every couple of years. My only suggestion is to stay the heck away from Oracle.

[w1andsodidwe]

I can relate having programmed for about 35 years, always build from scratch, build it to last, not to throw away and start over every couple of years. My only suggestion is to stay the heck away from Oracle.

Amen to that. Oracle appears to me to be just a big labor intensive waste of time. We have systems that will only run on it after being told that the purpose of relational databases was portability. Now can only use oracle with certain system. Just ignorance wanting to go that direction.

[Mr. K]

If John has been programming since age 14 I HOPE he went to college for Compter Science

Some of the best programmers I ever met were ALSO from a background like that- but without a background learning the fundamentals you might now have the best DESIGN abilities.

I have a computer science degree AND a physics degree.

I had to teach them a lot, about why you do things certain ways, but I also learned a lot from their long years of experience.

I think you have a fundamental database design problem. Not beyond repair.

Call up MDBS and ask them about TITANIUM (CODASYL networked database model)

I bet there are some freepers there

[T Minus Four]

Throwing more money at the problem won't solve it

It will if the problem is not enough money :-)