DSXchange

That ".dbf" extension means a dBase file and so yes, you should be able to access it via the ODBC stage using the supplied dBase driver.

Rows must flow through the job in order for something to be written to your target sequential file. What I'd suggest is checking the file 'after job' either from the operating system or a custom routine. If should be simple enough to see if the file is empty and if so, cat / echo your "2" ...

rumu wrote:In our client place DS tool has not been installed and hence we are not in a position to test anything

Just an FYI - this would have been something worth mentioning in your original post.

Terala - just an FYI. Your "code" and "quote" tags are not working because (I assume) you have checked/enabled the Disable BBCode in this post option for some reason. Uncheck that or change the default in your profile and they'll work as designed.

That comes from having the option "Automatically handle activities that fail" turned on as routines that do not return a zero value are considered to have failed. It should also have mentioned the fact that it is an "unhandled" failure and the secret to making it go away is to (i...

What exact warning are you receiving? The fact that it doesn't return a zero value? These can be dealt with, there should be no need to go under the covers for something like that.

Well... not sure I would have ponied up some of those thoughts if I'd known we were talking about two million files daily. Except perhaps academically.

I think your "Option 3" is a perfectly valid solution, kudos for coming up with that.

In a Server or Sequence job, sure.

Any idea why there's an issue with "complex" sql? What the issue actually is? Does "complex" equal "really really long" here?

Hmmm... not really, unless you know how many max you'll have ahead of time and build that many output stages into your job. Typical answer would be to create a single file and then script something after-job to split the file into multiple files with the names you require. Another answer might be to...

I'm curious, is there a particular problem you are trying to solve? Always best to ask about the bigger picture issue rather than focusing on what you perceive to be the solution to it. We've gone on many chases of the wild gooses here when people go down the wrong path, especially when there's a si...

In other words, the short answer is "just type it in".

Assuming the same number (and datatypes) of columns are being selected, you may simply be running out of room for the query, i.e. there is a maximum length to the query string that can be passed and it may be getting truncated. First suggestion would be to try removing all of the CR formatting, esse...

Welcome. :D It will fail. You cannot create job parameters other than at design time using the Designer. That function "sets" or assigns a value to an existing parameter. Besides, what good would the ability to create parameters "on the fly" be as they wouldn't actually be used i...

Hmmm... 13? New number here. Sure, leading spaces can be trimmed from a char field. It's the trailing ones being discussed as problematic here, the "padding" that is automatically done for the data type to its full size. Sorry if that wasn't clear.