Please post the text of your error message.

OK - you're using a space as a field delimiter. A bit risky unless you are sure that your data cannot contain even a single space.

So you need to check...

It's surely obvious to you why this is happening. You are using the comma for two purposes.

Please confirm what you would like the output file to look like.

Get Great Plains' database schema, build a mapping document, then write the conversion in SSIS.

Use a UNC path rather than a mapped drive.

--edit

You could also try changing the Success Value to 1 - if you think that the batch file is executing OK.

Tim Weintz (3/24/2010)

---

Another option is to load all data into a single column and write custom code to parse it, afterwards. Similar to the idea of loading it into an...

If all else fails, you could always look at using one of these[/url].

No I haven't - I've just read about other people's pain with XML. I try to stick with good old CSV's wherever possible. So I'm not the voice of experience...

Try creating the table first (outside of the package) and then importing, to try and narrow down where the error is occurring.

That is incorrect. Full debugging features are available for...

🙂 er ... perhaps I should have...

Or add @@SERVERNAME to your SELECT statement?

I presume you meant faster.

I'd like to see the proof. 'Always' is a big call.

SSIS is optimised for data flows pretty much by default. An...

Expressions allow you to use variables, but not to assign their values.

Thanks for posting back & glad to hear of the happy ending 🙂