![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Still no improvement about how Paradox can handle Unicode databases (meaning, almost no way) ? |
#3
| |||
| |||
|
|
Since development on the BDE is non-existent it isn't likely to change how it handles unicode on its own... ========================== |
)
#4
| |||
| |||
|
| Here is the message from Michel to connect to the Zoo |
onx|
Still no improvement about how Paradox can handle Unicode databases (meaning, almost no way) ? -- Cordialement Alain Godet ajouter un t avant le @ pour répondre... |
#5
| |||
| |||
|
|
Still no improvement about how Paradox can handle Unicode databases (meaning, almost no way) ? |
#6
| |||
| |||
|
|
Still no improvement about how Paradox can handle Unicode databases (meaning, almost no way) ? Just an idea, not sure if it works.......... If unicode table was on sql server it might be possible to write sql select cast(fieldname1 as varchar(30)) as fieldnameInResult from tbl Use sql and submit it as passthrough sql to the sql server, and then use "cast" to return nvarchar(unicode) as varchar, a datatype that pdox can actually handle. Robert Wiltshire |
![]() |
| Thread Tools | Search this Thread |
| Display Modes | |
| |