Hi

I am having some trouble importing certain tables from an odbc database
(Sage Line 50). Most of the tables import without any trouble whatsoever,
however there are 2 tables (SOP_items and POP_items) that always crash dts
when it tries to import them. The DTS screen simply dissappears from the
screen with no error. I realise that it is beyond the scope of this
newsgroup to ask about the specific odbc database. However I was wondering
is there a log somewhere which might help me to shed light on what in the
tables is making it crash. To note I can import and link to the tables in
access with no trouble whatsoever. Thanks for your time.

Dan

There will be no DTS log because it sounds as though something is crashing
DTS. Have you looked in Event Viewer?
Have you tried SPing (What SP are you running?)?

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"IT Dep" <it (AT) isslimREMOVE_TO_REPLYited (DOT) co.uk> wrote

Thanks,

It has SP3 on it, just looking at the mdac 2.7 sp1, see if this sorts it.

Dan

"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

Change of plan, going to install Microsoft Data Access Components (MDAC)
2.8, didn't see the newer version at first. I already have SP3 of SQL, it
does advise that SP3a is only for versions below SP3, and as such I
shouldn't install it? Looked in the event log to see if there is any log of
an error, but there is nothing whatsoever. Thanks.

Dan
"IT Dep" <it (AT) isslimREMOVE_TO_REPLYited (DOT) co.uk> wrote

MDAC 2.8 doesn't seem to have made any difference. Any ideas?

Thanks

Dan

"IT Dep" <it (AT) isslimREMOVE_TO_REPLYited (DOT) co.uk> wrote

Since this is an ODBC data source, you can try to turn on
ODBC tracing on the box where the package runs. Make sure to
turn the trace off after you have crashed with tracing
turned on. You can then go through the tracing log file and
look for ODBC errors.

-Sue

On Tue, 2 Nov 2004 09:34:59 -0000, "IT Dep"
<it (AT) isslimREMOVE_TO_REPLYited (DOT) co.uk> wrote:

Hi

Thanks for the responses, I think that I have worked out where the problem
was occuring. There were date columns in those two tables which were
causing the crash. The dates were in the form dd/mm/yyyy as well as
mm/dd/yyyy, so no wonder it had trouble with the data - what a wonderful
accounting package, if only it used SQL as the native database! Thanks for
all of your help


Dan

"Sue Hoegemeier" <Sue_H (AT) nomail (DOT) please> wrote