O7 – Strange phenomenon with SQL Server (SOLUTION)

Good new Bruno!

Note that the sandbox thing you mentioned has been part of Windows since
Vista. You’re not allowed to make changes to the contents of Program
Files, just in case you’re a virus or anything nefarious like that. This
is why newer versions of Omnis have the firstruninstall folder.
Basically Omnis 7 or Omnis Studio 4 and older, best not to install them
in Program Files.

Cheers,

Bas

On 16/11/17 7:17 pm, bub wrote:
> Solution found
>
> Source of the problem was command
>
> Set Character Mapping {ANSI}
>
> Real Source of the problem was wrong contents in ANSI.INI
>
> Real Real Source of the problem is that Windows 10 has this funny
> behaviour of letting you copy a file to discover that the file isn’t
> copied, it goes into some sandbox, appdata, don’t know where but not
> where it was meant to be with the result that ANSI.INI was wrong…
>
> Doug, a bit fat thanks to you as you clearly pointed me to this
> ‘character mapping’ thing.  The reason VCS worked and my app not is
> because VCS Logon doesn’t issue this command ‘Set Character Mapping’
>
> Omg, what a journey this was…but oh so happy i can work now on my
> new shiny new workstation…
>
> Bruno Huyssen

_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com