Original User: jwickstrom
Hello Nate,
We have not seen that problem. Odd. I would blame it on the database driver had you not preempted that with the 3.x test! It would also be interesting to try this DSN from some other app (i.e. Excel or Access).
Does it make a difference whether you are using a saved import profile or using a new one?
So what happens when you do the import? Does it work?
If not, please add a support incident for it. If it works anyway, perhaps add a support incident with a lower urgency factor on it.
Thanks,
Jeff