O$ 4.3 Converting from non-unicode to unicode

[Mike Matthews]

If this is using the DF1, then definitely backup first, which re reading looks like it is.

Are using v5 or v6 of Studio, or staying with v4 unicode (does it exist?)

Anyway, using DF1:

When prompted, do the FULL conversion, if you have foreign characters, they cane destroyed between Mac and Windows users.  I know this, it happened to me, I took the QUICK option, bad mistake.

Apart from that, I had to to no other mods for the application that came from 07 days, but other methods that write/read text files, etc, may need to be updated.

Mike



Mike Matthews,
 Managing Director, SQLWorks Software Ltd

Tel: +44 (0)1271 850 550

Email: mike.matthews at sqlworks.co.uk

Web: www.sqlworks.co.uk

SQLWorks replaces Sage, ACT!, Opera, Access, SAP

On 22 Jul 2013, at 22:16, Fred Moseley <fredmoseley at sbcglobal.net> wrote:

> What is the best approach to do this:
> 1. Trust in the Omnis Studio conversion tool
> or
> 2.  Export my data. Convert to unicode with some other utility.  Then import data into a new unicode omnis datafile.
> 
> Any common issues I should keep an eye out for after conversion?
> 
> Any help will be greatly appreciated.
> 
> TIA_____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com