DSXchange

chulett

Yah, that's basically a 'no'.

chulett

Not sure how you can expect anyone on the other side of the looking glass to be able to answer that.

chulett

The error message says it all. What is the metadata for the hashed file being written to? Have you checked what you are sending to the key fields?

chulett

What I built for my test:

Code: Select all

If Index(Arg1,'E',1) > 0 Then
  Ans = 'TRUE'
End Else
  Ans = 'FALSE'
End

chulett

Is "SQL Server 2005 Express Edition" anywhere on the supported repository database list for 8.x?

chulett

I'm perfectly well aware of that, hence the question I ask earlier - does this work differently or require different syntax on that older version? Any clue?

chulett

Just built a little test harness in the Manager and it worked fine for me.

chulett

What "doesn't work" about it? Your syntax (assuming you add back the paren that is missing) is perfectly valid... unless it works differently in 5.x?

chulett

Index()

chulett

If you want the lookup to return multiple records, you'll need to use either a UV stage or an ODBC stage for the looking upping.

chulett

Sounds fine to me but obviously we're missing something if it isn't working for you.

chulett

Isn't this just a matter of setting PRESERVE_BLANKS to false during the load? Also assuming the target field in Oracle is a VARCHAR2(11) and not a CHAR(11), yes?

chulett

Hashed files are not database tables that support dynamic metadata, the Key and Non-key (data) fields are positional. So (at a high level) all columns must be mentioned in the proper order or the data will appear to 'slide around' into the 'wrong' field.

chulett

I doubt it, this would need to go to Support I would think.

chulett

Suggest you Google for the error. For example:

http://www.orafaq.com/usenet/comp.datab ... 7/1877.htm

Search found 42189 matches