-
Oracle Lite and bad charset in tables after synchronize
Hi all,
I have any tables and data are stored in UTF-8. With this database I
synchronize. After synchronization process are data (on client PC) in
bad character set (and bad date/time format, etc.).
Does anybody know how to synchronize data to client at UTF-8?
Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
Mobile Client is a WindowsXP. Oracle 9i lite.
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel
-
Re: Oracle Lite and bad charset in tables after synchronize
MI'RA wrote:
> Hi all,
>
> I have any tables and data are stored in UTF-8. With this database I
> synchronize. After synchronization process are data (on client PC) in
> bad character set (and bad date/time format, etc.).
>
> Does anybody know how to synchronize data to client at UTF-8?
>
> Mobile server is on Linux RedHat, Mobile Repository is on the Windows,
> Mobile Client is a WindowsXP. Oracle 9i lite.
- How do you synchronize?
- how do you know you have a bad characterset?
* The date format is just a display setting; dates
are internally represented as numbers. Therefor,
this does not count as proof for bad characterset.
- make sure the client characterset is UTF-8; yours
is probably WE8MSWIN1252 on the Windows side.
--
Regards,
Frank van Bortel