x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 6 replies
  • Subscribers 58 subscribers
  • Views 2504 views
  • Users 0 members are here
Browse Forums
Sage Timeslips Anywhere Announcements
6
topics
1
replies
Sage Timeslips Anywhere General Discussion
13
topics
13
replies
Sage Timeslips Premium Announcements
57
topics
17
replies
Sage Timeslips Premium General Discussion
2k
topics
8k
replies
Claire98

Upgrading V2009 Db to V2014

SOLVED
Posted By

This is an unusual one.  A customer is upgrading from V2009 to V2014.  After Timeslips upgrades the database it comes up with this error.

------------------------------------------------------------
The database is a different format than expected. It may have been created with a different program. It cannot be used here.

Area: Database

Error Code: 5

Class: tBDEDatabaseExceptionC

Version: 22.0.2.256

Date: 27/03/2014

Time: 16:46:04

Exception tBDEDatabaseExceptionC in module Timeslip.exe at 00924371.

------------------------------------------------------------


I then went back to the original 2009 database and performed a stepped upgrade (2009 to 2010.  2010 to 2011 etc).  It upgraded all the way to 2013 with no problem.  When I try to upgrade it to 2014 the above error appears.

The upgrade of the database is being performed on the local machine
It's a Windows 7  machine
I have Administrator security rights.

I've never seen the likes of it. Any ideas?

Parents
  • 0

    Did you look for PDOXUSRS and Paradox lock files? That can cause errors along the lines you are describing. Doesn't sound like they should be there given the upgrade process but worth a search.

  • 0 in reply to Caren2

    Thanks everyone

    1) Conversion log: The log says that everything converted successfully. Nothing looks like it's gone wrong

    2) Data Verification on 2013 reports no errors

    3) There were no Paradox lock files. The only PDOX file that was available to delete was PDOXUSRS.net. I deleted that but come up with the same results

    I have been upgrading the database with SR1 and SR2 applied.  I tried to convert the 2013, working, database using a version of Timeslips 2014 with no SRs applied and I still get the same problem.

    To ensure that it wasn't a problem with my installation of Timeslips, I took the demonstration database from 2013 and upgraded it to 2014.  There were no problems and it upgraded and opened without issue.

    I am about to compare the files from the faulty database with a working 2014 database and see if I come across any differences. Will report back if I find anything.

  • 0 in reply to Claire98
    verified answer

    After some faffing about, the problem lies with the Main files in the database. Either they've not been updated correctly by the conversion or there was some kind of corruption that the DV wasn't picking up.  After some data repair I can now access the database on 2014.

    Thanks for all your help.

  • 0 in reply to Claire98

    Glad you got this resolved Claire!

Reply Children
No Data

*Community Hub is the new name for Sage City