Ok, here's my 2 cents:

I believe if it can be done in SQL, then it SHOULD be done in SQL. I had a

time trying to get an xbase algorithm to work recently, and eventually just

wrote simple SQL to do the same thing. My SQL code was 3 pages long, whereas

the xbase code was over 9 pages long. I think the SQL was easier in this

instance, but of course, it all depends on what's called for in the spec.

Now I suppose someone might prefer to write tons of code if they read a

ComputerWorld article some months ago (I wanted to reference it but I couldn't

find it!) that said "...programmers should get paid for the number of lines of

code they write..." or some other crap like that. That paper article deserved

to be in the restroom to be used for a better purpose, like toilet paper,

although that might have been too good for it. <g>

Someone else (I think Cindy Winegarden) really hit the nail on the head when

she said how it is portable and not Foxpro dependent. That is SO true. And

if for some reason you're in a spot like Matt, you can take your SQL knowledge

and apply for those many Oracle or other jobs out there where SQL is used.

>>> "Chad@teche.net" 10/06/99 10:24am >>>

I wonder if Anders is available for hire since he is an SQL Guru.

Chad Bourque

U.S. Bankruptcy Court - 11th Circuit

Alabama - Northern District - Southern Division

Chad@teche.net