Professional Web Applications Themes

Bad data after migration Client Access v4.4 to v5.1 - IBM DB2

Dear All I have very strange situation with ODBC settings. I support application (VB) dealing with db on AS400. Some time ago I installed Client Access v4.4 and then I created ODBC data source to 'link' LIB_1 on AS and everything worked fine. Yesterday I have migrated CA to v5.1 and still everything was OK. But! Today I removed mentioned ODBC data source settings (for some important reason) and created it again. Unfortunately now I get bad-mixed data in the application. I have search win2k registry - ODBC setting and compared it with other PC where application works correctly (because ...

  1. #1

    Default Bad data after migration Client Access v4.4 to v5.1

    Dear All
    I have very strange situation with ODBC settings.
    I support application (VB) dealing with db on AS400.

    Some time ago I installed Client Access v4.4 and then I created ODBC
    data source to 'link' LIB_1 on AS and everything worked fine.

    Yesterday I have migrated CA to v5.1 and still everything was OK.
    But!
    Today I removed mentioned ODBC data source settings (for some
    important reason) and created it again.
    Unfortunately now I get bad-mixed data in the application.

    I have search win2k registry - ODBC setting and compared it with other
    PC where application works correctly (because there is still CA v4.4)
    and there were differences.
    I thought that modifying registry to set these settings/parameters on
    PC with CA5.1 as they are on PC with CA4.4 would help. But I was
    wrong!
    Now registry same connection looks the same and application still does
    not work properly.

    I have another ODBC setting on PC with CA5.1 to the LIB_2 (which is
    exact copy of LIB_1) and everything works fine – I think just
    because these setting were defined when there was CA 4.4 and after
    installing CA5.1 were not recreated.

    Registry looks this way:

    [HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ABCDB_02]
    "Driver"="C:\\Program Files\\IBM\\Client Access\\Shared\\cwbodbc.dll"
    "Description"="02: Server Datasource"
    "System"="AS4001"
    "CommitMode"="2"
    "MaxFieldLength"="32"
    "DefaultLibraries"="ABCDB02,ABCGM30P,QGPL"
    "SearchPattern"="1"
    "ManagedDataSource"="0"
    "ExtendedDynamic"="1"
    "DefaultPkgLibrary"="QGPL"
    "LazyClose"="1"
    "PreFetch"="0"
    "AllowDataCompression"="0"
    "RecordBlocking"="2"
    "BlockSizeKB"="32"
    "LibraryView"="0"
    "SortSequence"="0"
    "SortTable"=""
    "SortWeight"="0"
    "LanguageID"="ENU"
    "AllowUnsupportedChar"="0"
    "ConnectionType"="0"
    "ODBCRemarks"="0"
    "AlwaysScrollable"="0"
    "ForceTranslation"="0"
    "TranslationDLL"=""
    "TranslationOption"=""
    "CCSID"=""
    "Naming"="0"
    "DateFormat"="5"
    "DateSeparator"="1"
    "TimeFormat"="0"
    "TimeSeparator"="0"
    "Decimal"="0"
    "PackageMSACCESS"="QGPL/MSACCES(VBA),2,0,1,0,512 ; *CHG"
    "Packageposmain"="QGPL/ABCMAIN(VBA),2,0,1,0,512 ; *CHG"
    "Packagevb5"="QGPL/VB5(VBA),2,0,1,0,512 ; *CHG"

    My questions are:
    1. Why application works improperly just after recreating ODBC
    settings?
    2. Are there any hidden parameters of CA (in registry on somewhere
    else on PC) that cause problem in my situation?

    Thanks in advanced for any help.

    Krzysiek
    Krzysiek Guest

  2. #2

    Default Re: Bad data after migration Client Access v4.4 to v5.1

    In the ODBC, you need to put that the driver converts de CCSID 65535 (by
    default it is not activated).
    Try it

    Krzysiek escribió:
     


    Grup Guest

  3. #3

    Default Re: Bad data after migration Client Access v4.4 to v5.1

    Hello
    Unfortunatelly it did not help...
    Krzysiek

    "Grup ANTAIX S.A." <com> wrote in message news:<com>... [/ref]
    Krzysiek Guest

  4. #4

    Default Re: Bad data after migration Client Access v4.4 to v5.1

    Hello again.
    There is one more thing:
    When I run application from VB environment everything is OK but if I
    compile a new executable and run, it is not!
    I have checked many configuration and options in ODBC settings and
    noticed that application (no matter if its started from .exe or VB)
    works correctly until "Commit Mode" <> "Commit immediate".

    For "Read uncommitted (*CHG)", "Read committed (*CS"), "Repeatable
    Read (*RR)" it's OK.

    Have you any ideas?
    PS. I found in Windows Registry a parameter:
    "Packagevb5"="QGPL/VB5(VBA),2,0,1,0,512 ; *CHG"

    Do you know what does "(VBA)" stands for?
    Sometimes there is (VBA) or (FBA) or (FRA)...

    Best regards,
    Krzysiek

    pl (Krzysiek) wrote in message news:<google.com>... [/ref][/ref]
    Krzysiek Guest

Similar Threads

  1. Replies: 6
    Last Post: May 5th, 06:17 PM
  2. MS SQL 2000 Data Migration w/ ColdFusion
    By ajsolimine in forum Coldfusion Server Administration
    Replies: 3
    Last Post: December 14th, 06:18 PM
  3. Replies: 0
    Last Post: November 14th, 10:39 PM
  4. Extending client to access Excel files (most data still in SQL Server)
    By Christopher Stolte in forum Microsoft SQL / MS SQL Server
    Replies: 3
    Last Post: July 16th, 01:40 PM
  5. XP, IBM Access Connections, Cisco VPN client, Novell client
    By Jonathan in forum Windows Networking
    Replies: 0
    Last Post: July 11th, 06:56 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139