>> >>> i can again create my usergroups and tables and import some >>> data, but in >>> the moment the access-table contains a german umlaut access brings the >>> error "[SAP AG][SQLOD32.DLL][SAP DB]General error:-8046 Pos(632) >>> Conversation from UNICODE impossible AC20. (#-8086) >>> >> >> This is done on instance creation and can't be changed. You need to drop the >> database and create it with UNICODE=YES. >> > >i will see, i dropped the instance and recreated with the extended parameter >_UNICODE=YES (i left this unchanged) and set DEFAULT_CODE from ASCII to >UNICODE. > > >now the import works (even with the german umlauts). but i was 100% sure >before that the parameter was set ASCII before. > >i will check the test's when everything is inserted.
ok after several trials, i figured out DEFAULT_CODE was ASCII before. the error above comes, when _UNICODE=YES and DEFAULT_CODE=ASCII so i can import with access97 and sapdb odbc 7.4 (cause 7.5 doesnt work on the old windows nt4 for me) when: _UNICODE=YES DEFAULT_CODE=UNICODE but then our app cant read all data, cause it isn't complete unicode compatible :( and it works when _UNICODE=no DEFAULT_CODE=ASCII >> >>> 2006-08-03 14:24:27 3506 ERR -11987 COMMUNIC kernel released >>> connection! >>> >>> 2006-08-03 14:41:25 3609 ERR -11608 COMMUNIC sql03_request: wrong >>> connection state, state is 'requested' >>> >> >> I remember this error but I believe it's fixed already in later versions >> (haven't seen it yet for a long time). >> >i think this was a overfilled /tmp/ where i tried to save the output. >will also come up, on the next test, but this will take a while. this was the full /tmp/ :/ -- # Thomas Stegbauer # https://keyserver1.pgp.com/vkd/DownloadKey.event?keyid=0x9A3F1866FC68E91D # Key fingerprint = 5A2D FEDC 8A50 F1BB 25FB 967B 9A3F 1866 FC68 E91D -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
