DSXchange

What you should do is create a project in production for emergency bug fixes and do them there. You're introducing a chance for more errors and unaccountable issues. Or, re-install 7.1 on the same development server (both can be installed). Next time you do an upgrade like this, you need to co-insta...

ppalka wrote:There was enabled "record level read" option in source hf. After disabling it I get good results. So is it the bug of DS? I think this option should work fine ...

Why did you check this is in the first place?

Edited my original response.

<< Wrong!!>> Yeah, it's PX.

Okay, I read Enterprise, but it's really Extended. My eyes are a little blurry, had a busy day. :D

By the way, I can tell you the difference between Extended Memory and Expanded Memory as well.

The fact that you are asking this question motivates me to ask: do you really think this is a good design? How about moving a lot of that logic into a custom function or buildop?

Turn off row-buffering, write-caching, and inter-process and try again. I can't really tell you what you're doing wrong, but it could be a bug.

You don't define it, you just do it. If you mean embedded CR or CR/LF in a text field, it's supported. Just make sure if you try to read it back you configure the Sequential stage with quotes, check contains embedded CR/LF, etc.

Spool to a file at the same time and see what the result looks like. Spool all values used in the function to the file as well as the result from the file. Look for what's wrong.

If you doubt the output, add an extra link to go to a Sequential file. Are you expecting sorted data in some fashion and using stage variables with COMMONs? Define unreadable data.

Welcome aboard. Your answer is no.

Why not build a job that resolves a "full" price file and a "partial" price file into a single dataset? In other words, union the two files to have a more complete set. Then, you have a consistent reference set that is supposed to be everything.

Are you saying that instead of a full file with all columns including price, they send you just a file of the product id and price, how to handle this?

The answer is tell them to send you the full file every time.

How do you know when you've received a full file and not a partial file? Is it because another file which references the product file doesn't match to any products? What you need to do is setup a staging mechanism where new facts are staged, probably in a database, with a status column indicating re...

I don't know of an MS-Access ODBC driver for Unix. One method is to use a SQL-Server database and connect the MS-Access mdb to it, then use the SQL-Server ODBC driver for Unix.

chulett wrote:Reinstall your client software.

Yup.