Date stamp error while importing to Access

[kruelkop]

I get a date time stamp error while importing data into Access from APHDR and OEHDR files. Some of the date fields give me this error not all. Any solutions ?

 

[bbrendan]

hi,

what version/package are you using?
As in version 7.2 Ebackoffice the table for orders is
orders
date fields are datetime

should work, as I do import into orders all the time!.

Note. on the AP side they use julian dates

hth
brendan

 

[kruelkop]

Hello,

Am using Pervasive 7 with PFW 4.6. The date fields are Date type.

 

[bbrendan]

Sorry havent used Pervasive 7 on PFW4.6

whats the error message you get?

 

[kruelkop]

Here's the message :

ODBC -- call failed.

[Pervasive][odbc Client Interface]Invalid date, time or timestamp value. (#0)

This is what Access help says but is misleading since this is not the case.

"ODBC – call failed. (Error 3146)
Using an ODBC connection, you tried to perform an operation on data in an ODBC data source. This error may occur when the ODBC data source is on a network drive and you are not connected to the network. Make sure the network is available, and then try the operation again."

 

[Flloyd]

My recollection is that Platinum had published incorrect .ddf's for the 4.5 through 4.8 releases. You may want to check the support site to see if you have the most current .ddf's for the 4.6 release you are on. Lloyd Freiday

 

[korzen]

I'm having the same problem, but I'm also having a hard time locating this information on the CA support site. Does anybody know where I can find the latest DDFs?

Chris Korzen
Boston, MA

 

[grnelson]

It might be an issue with invalid dates which Btrieve will store but Access has a problem. check out this link as it leads to a date fixer program. I have not used it but came across it the other day. I use PFW also and the dates are 4 byte Btrieve dates which the ODBC drivers should recognize if the data is valid.

Gil

http://www.pervasive.com/ComponentZ...oryID=6&Page=1&CategoryName=Tools+/+Utilities

Gil