DSXchange

Just wanted to add that the good thing (or perhaps bad thing) about the Conv conversions is that if you do something invalid they typically don't throw an error but rather pass the original value through unchanged. Which is why doing an 'unnecessary' IConv on an internal date seems to work properly....

Convert("/:","",Oconv(Iconv(internal_date, "D2/"),"DYMD[4,2,2]")) So... basically the same answer as posted in 2006 with semicolons added to the strip list (it's a date not a date/time) and an unnecessary IConv thrown in for some reason... if you are truly de...

As it should be.

A file that starts with 'ViewData' I would assume is generated by the View Data process and for whatever reason failed to clean it up. Perhaps the client session aborted or was force closed? Nuke it.

Database. Let's start with - do you have an index over the fields in your update where clause?

... if not using RCP. Just calling that out again.

Also note the docs specifically say Record Count rather than Transaction Size should be set to zero...

Make sure you have all the latest fixpacks for your version and if so, involve support.

Looks like the official answer is to set Autocommit mode to off and Record Count to zero. If that's not working, then I would involve support.

Sequential files are not relational tables where you can pick and choose the columns you want. ALL must be read, at least up through the last column that you need and that only if your tool can support short reads. What you do with them after that is up to you.

Have you involved your official support provider yet?

yijuanl wrote:But after deployment, the browser shows only one record.

Is this actually a problem? XML doesn't require any 'fomatting' and can present itself as one long record... I am thinking JSON would be the same. ??

Can you post the 'abort' you are getting? Don't understand why it would think a # is a delimiter so wondering if the actual abort text might help clear that up.

Oh, THAT log. Never mind.