CODEWITHSUNDEEP
ms-accessodbcpervasivepervasive-sql
boilers222
boilers222

Reputation: 1989

How do I fix an Access database using Pervasive client that breaks after upgrading to Access 2016?

Have a client that upgraded all of their machines to Access 2016. Before, they had a mixture of older Access versions. The access databases they use have an ODBC connection to a Pervasive database. I don't know anything more about Pervasive. I know in the past when they've had a single machine go to Access 2016 or from older versions of Windows to Windows 2010 and I've had to re-link tables.

Right now, they're getting this error:

ODBC-call failed [Pervasive][ODBC Client Interface][LNA][Pervasive][ODBC Engine Interface]Invalid date, time or timestamp value. (#0)

I need some suggestions on how to fix this for all machines and all Access applications.

** UPDATE ** The problem was a missing Active X calendar control. I changed all the date controls on the form to be text boxes to take advantage of the new Access calendar pop-up. The problem now is that the client has dozens of Access database. As far as I know, I'd have to open each file and each form in the file and change the controls one at a time. Anyone know of a way to update multiple Access file without having to touch them all?

Upvotes: 0

Views: 380

Answers (1)

jhTuppeny
jhTuppeny

Reputation: 970

The calendar control will still work with Access2016. If you've got loads of databases it's probably quicker to re-install the calendar control.

You will need the MSCAL.OCX file which you can download. Copy the MSCAL.OCX file to c:\windows\sysWOW64 not c:\windows\system32. Register it by running from the command prompt or run in the start menu

regsvr32 c:\windows\sysWOW64\MSCAL.ocx

and it should register OK but make sure that you run regsvr32 with administrator privileges.

Upvotes: 0

Related Questions