| Visual Basic |
| Crystal Reports |
| SQL Server |
| Lotus Notes |
| FoxPro |
| MS Access |
| |
|
| |
The Trouble with Consultants |
| |
The trouble is, they're too fond of their code. They make it as
efficient, and therefore as cryptic, as possible. Ever invite some consultants to do
work for you? They leave in October, and their date code fails on Jan 1. |
| |
And it's impossible to figure out why. That's because they love
to do that, write one huge SQL statement, brilliant, with left joins and "isnulls"
flying all over the place, but nobody can figure it out, and now you're stuck.
|
| |
We don't do that. Barring execution-time constraints, we
might put all the fields into a temporary table and update
them one field at a time. That way, you can pinpoint the
problem on your own. Other consultants never do that. |
| |
Hey, we don't know everything, so we leave
you with the easiest way to solve your data problems. |
| |
We annotate everything. We'll put in a statement like,
"If you have double pricing here, check for duplicate values
in your branch-plant table." We might even write a whole
remarked-out paragraph that you can use to test this
particular field for data problems, right in the code. |
| |
There are many ways to write a computer
program. Simplicity is the mother of experience (or
something like that). We try and leave you without a lot of
anxiety. |
|
