DSXchange

You keep us laughing. Therefore not soo serious.

Thanks Mr. Craig.

It is hard to take Mr. Craig too serious but that is why we appreciate him.

You could also look at processing an export in XML format and not the normal DSX format. Should help get specific things quicker.

Look at UtilityRunJob in the SDK.

dsjob -report is also useful.

Why do you need to do this?

Mr. Craig.

I forgot search is a advanced concept. m I think the path is included in the file name. You would need to look for slashes (either \ or / based on the OS). The absence of slashes says the file is in the project directory. The # should exist in a parameterized version. It should be easy to check for ...

First of all you need to name your links. When you set limits to 2000/50 then you told it to stop after 2000 rows or 50 warnings.

What?

Wrap this command in a batch file then execute the batch file. It may work better.

I posted SQL recently which will allow you to find these jobs quickly. You could QA them before they are promoted to production.

I think in 7.5.1 you can create variables in a sequence and reuse them. I think in earlier versions that all the arguments of a routine are available in the sequence after th routine has been called. So yes they should be resuable.

Do a search there is lots of code posted showing how to use these routines. As far as getting row counts from source tables then create a job that select count(*) from #TableName# Put the result in a hash file with the parameter TableName as the key. Use UtilityHashRead or whatever the SDK routine n...

Keep going to you find your table. This is how you figure it out. You don't need 7,1. You need to find the right field.

If you post your OLETYPEs then maybe I can help. If I have some jobs with these OLETYPEs then I can find it faster by editing the records.