| Title: | The Replication Option for Rdb |
| Notice: | Product renamed to Replication Option for Rdb |
| Moderator: | BROKE::PROTEAU |
| Created: | Wed Mar 02 1994 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 287 |
| Total number of notes: | 1231 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 63.1 | We are looking at this problem now with SYBASE... | BROKE::WHCOX | Bill Cox, Database Systems (ZKO2-1/N26), (DTN) 381-2546 | Wed Jul 27 1994 09:37 | 20 |
| 63.2 | Any developments | ORAREP::CHEFS::MACLEOD | Tue Apr 30 1996 10:26 | 5 | |
Any news on this problem. Is there a later version of ODBC (our's or Microsoft's) that can cope with Quadwords. Ferdy | |||||
| 63.3 | BROKE::PROTEAU | Jean-Claude Proteau | Tue Apr 30 1996 11:08 | 13 | |
You'll need version 7.0 of our product. It encodes the database key as
CHAR(16), converting binary bytes into two ASCII text characters by
splitting bytes into two 4-bit nibbles and converting the binary values
into their equivalent ASCII codes. In this way, only text strings are
stored (no null bytes).
Version 7.0 is in beta test.
For anyone needing a solution for transfer into Sybase databases,
version 6.0-11 has a fix (but only for Sybase).
Claude
| |||||