Recently (within the last 2 months) we began having a
problem using DTS for conversion of DBFs that have a
Logical field. The field, which is logical in Clipper, is
never null in the DBF when viewed from DBX, but the
results from DTS are definitely incorrect. (We verified
through DBX that only 13 records out of 15,000 were true,
but DBX yielded over 10,000 records as true.)

This problem only occurs when a client machine running the
Enterprise Manager initiates the job. The client can be
98, 2000 and XP. When the same job is run through
enterprise manager directly on the server, the results are
perfect.

As a side note, but possibly related, We have always
imported DBFs into excel for basic work and lists and
until the last couple of months this worked as perfectly
as SQL DTS. Now though, the logical field imports in as 0,
1, or null AND THERE ARE NO NULLS! only true and false.

Please Help

You could write an ActiveX script to convert the 0 and 1 to true and
false while importing.

Regards

Partha Mandayam
Software Consultant
Home page: http://partha.tripod.com


*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

In news: c2f601c43859$65fb9d90$a501280a (AT) phx (DOT) gbl,
Allan T <anonymous (AT) discussions (DOT) microsoft.com> wrote:
Hi Allan,

I don't work with Clipper DBFs but I do work with FoxPro DBFs. In FoxPro a
date field can have a value of .T. or .F., or it can never have been given a
value - it is considered "empty." The ability to set a value of .NULL.
didn't come until later versions of Visual FoxPro, but an "empty" date is
still different from a .NULL. date.

For comparison purposes, an empty date will evaluate to .F. in FoxPro.

I'm sure you're getting nulls for the "empty" dates. You'll have to think of
a way to turn those values into False values.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden (AT) mvps (DOT) org www.cindywinegarden.com