Theres an expression out there: Theres a million
ways to skin a consultant. Any way you choose to do
it, the underlying necessity of a library of routines
still exists. This thread started as a request for
help in BASIC.
My recommendation is to develop this library, and code
it per the business rules of the client. Youve seen
the bag of tricks Ive been handing out. That is a
helpful starting point for many clients. They can
build from there according to their needs. If you
poke thru the folders in Manager after the import, you
see a bunch of functions and routines that handle
dates, conversions, etc. All clients end of
developing these, so the sooner you get started on
these the more successful youll be. And dont let
tech support tell you how much it slows down jobs, as modularity and reusability should be higher priorities when writing code.
Thanks,
-Ken
--- Ray Wurlod wrote:
> Ken,
>
> I admit it, but then I always use
> Ans=Not(Not(Len(Arg1))) as my Exists
> function. Put the rest down to carelessness.
> In fact, just Ans=Len(Arg1) would do, since 0 and ""
> are regarded as false,
> and any other non-null value is regarded as true in
> a Boolean context by
> DataStage.
> By the way, have you tested your Exists code with "
> " (that is, a single
> space - or, for that matter, any number of spaces
> and nothing else) as the
> argument? However, lets not get into a
> philosophical discussion about
> whether a space exists.
> You will also find that your function returns
> "false" if the data is made up
> of any trimmable character (such as tab). The
> difficulty is the Trim()
> function, of course. Whether or not data should be
> trimmed is a separate
> argument from a test for existence, which must be
> answered on a case by case
> basis. Your business rules, whatever they are, have
> to be implemented.
>
> Regards,
> Ray
>
>
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger.
http://im.yahoo.com