Re: Date * 10000.01

> -snip-
> 
>         [And Brad Said:]  ARGHH!!!! TOO MANY @s!!!!!!!!  :)

That's a level 10 compiler error, isn't it? ;^) 

> 
> Actually, I rather agree with that, but when you're working across 75+ 
> machines and you didn't write the original code, it behooves you to find
a 
> naming convention that won't step on the existing field names.  In 
> addition, I can easily scan/replace these wierd names if I need to.  As 
> ugly as they are, it beats trying to write RPG apps that use a Synon 
> database!  :-)

Yuck! Randomly generated fields names, what a great idea!  Why, once you
have Synon, you will never access your database any other way again.  Throw
away your query tools.  Never memorize another field name (because you'll
never be able to anyway).

And while you're at it, why don't you join all your files together into
great big logicals?  And define them all as UNIQUE.

:^)  O.K. I feel better now.

Always much more fun to be the designer, rather than the person who comes
in later and makes it work...

p.s. don't multiply. ;^)

Kathleen Kostuck
___________________
(414) 402-0820       fax (414) 495-4986
kkostuck@execpc.com
AS/400 Solutions
Secretary - Wisconsin Midrange Computer Professionals Association   
___________________
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---