Date parsed: 5/31/2002 12:53:15 PM
Date: Fri, 31 May 2002 11:53:15 +0200
Chris,
thanks for the file.
I looked at the design of the table and could immediately see the cause of
your problem:
Your table has two columns, DateTimeRFC822Local and DateTimeRFC822UTC, both
of type "Date/Time".
This is wrong, these two columns must be of type "Text".
SL4NT 1.x & 2.x did just ignore this columns because they had the wrong data
type, SL4NT 3.0 now tries to convert the datatype which fails for these two
columns.
Please remove these two columns, DateTimeRFC822Local and DateTimeRFC822UTC,
from your table(s) or change their datatype to "Text".
Franz
"Franz Krainer" <franzk@netal.com> wrote in message
news:M6PL9WICCHA.2048@is1.netal.com...
> Chris,
>
> please send me one of your .MDB-files for analysis.
>
> Thanks,
> Franz
>
> "news.netal.com" <chris.clemson@softwareag.co.uk> wrote in message
> news:L2W4TVICCHA.2048@is1.netal.com...
> > I have been using SL4NT v2.1 for a while now, and soon after i got the
> email
> > about the new version, i upgraded.
> >
> > The only problem is that the new version doesn't seem to be logging to
my
> > ODBC data source anymore.
> >
> > in the event log, i get the following:
> >
> > Event ID: 50
> > Source: SL4NT
> > Description:
> > Inserting a new log record into the table <syslog> of the database
> specified
> > by the DSN <syslogd> failed. ODBC reports the following errors:
> > 22005 [Microsoft][ODBC Microsoft Access Driver]Invalid character value
> for
> > cast specification (null) (Native error code: 39)
> >
> > followed by:
> >
> > Event ID: 48
> > Source: SL4NT
> > Description:
> > One or more ODBC operations related to the action <syslogd> failed.
> >
> > the "syslogd" database is an Access XP .mdb file, which has been working
> > fine for ages.
> > SL4NT is running on NT SP6a.
> >
> > any ideas what this means?
> > it sounds like it's a trying to convert data from one format to another,
> but
> > i don't know much about access.
> >
> > TIA,
> > chris
> >
> >
>
>