Article ID 2237
Article Title HOWTO: Upgrade Connectivity Kit and Convert DFRECNUM Tables to RECNUM Tables
Article URL http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2237
KBase Category Connectivity
Date Created 08/22/2006
Last Edit Date 08/22/2006


Article Text
QUESTION:
I want to migrate from Microsoft SQL Server Connectivity Kit 2.2 to 4.1. How should I go about changing my DFRECNUM tables into RECNUM tables?

ANSWER:
To upgrade CK revisions you don't have to remove DFRECNUM. A 3.x or 4.x driver can handle DFRECNUM tables with no problem. If you just drop a 4.1 CK in an environment created by a 2.2 CK, you can open the tables and everything should work just like it did before.


But if you want to change the table structures to replace DFRECNUM with RECNUM, you should:

1) Delete the DFRECNUM column (in the column tab in Database Builder)
2) Set the primary index to 0 (in the Parameters tab in Database Builder)
3) Save the table definition

Make sure you review your indices. If you have indices that contain DFRECNUM as a
segment, you may have to change their definitions once you make the switch to Recnum.


Note:
When you upgrade the Connectivity Kit, the CCHs will be recreated (because the revision of the driver changed). It would be better if you ran the application (or opened all the tables) ahead of time so the users don't need to wait for all the CCHs to be recreated when starting the application, i.e. opening a table.

CCHs are automatically deleted when you restructure a table. So, if you removed DFRECNUM from the tables, you will not need to do anything about the CCHs.




Contributed By:
Ben Weijers
Company: Data Access Worldwide
Web Site: http://www.dataaccess.com

Links Related to this Article
DAW Knowledge Base article 1643: INFO: When Cache Files from Connectivity Kits should be Deleted

Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.