Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Forum Replies Created

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • in reply to: Sqlyog 5 And Windows 98 (i Know….) #19709
    reinaldo
    Member
    peterlaursen wrote on Nov 18 2005, 06:33 PM:
    @ritesh

    could it be a localsation issue?

    The folder name 'Program Files' is translated in localised Windows versions for instance.  In Danish is is 'Programmer'.  The symbolic '%Programs%' is substituted with the real name and should be used.  But you probably know!

    I suspect that something went wrong when you coded the ability to write to 'Documents and Settings' (that for some strange reason is NOT localized!).  If neither 'Program Files' nor 'Documents and Settings' exist then it could fail to read ini file, if it is hardcoded that way.  And 'Program Files' does not exist in localised Windows and 'Documents and Settings' not in W98. But I have no W98 to test with.

    Just my guess that it is something like this  <_<

    [post=”7924″]<{POST_SNAPBACK}>[/post]

    I just have tried to install in c:program filesSQLYog but the problem remain.

    Thanks for your help

    in reply to: Sqlyog 5 And Windows 98 (i Know….) #19706
    reinaldo
    Member
    Ritesh wrote on Nov 9 2005, 02:59 AM:
    This is very strange. We have tested 5.0 in Win98 and it works great.

    What is the error that you are getting?

    [post=”7857″]<{POST_SNAPBACK}>[/post]

    I have the same problem. Just nothing hapens. I double click on icon and nothing. The SQLYog 5 didn´t start. The version 4.07 works fine, but 5 not.

    My operational system is Windows 98SE.

    Thanks in advance and sorry about mistakes in my english

    Reinaldo Melo Filho

    Recife-PE-Brazil

    in reply to: copy database error #16648
    reinaldo
    Member
    Ritesh wrote on Dec 6 2004, 02:41 PM:
    SQLyog uses the query returned from “CREATE TABLE…” SQL to create tables between two hosts. It looks like the SQL returned from 4.0.17 is not compatible with 4.1.7.

    I have forwarded the issue to my development team.

    Ok, but I using from 4.1.7 to 4.0.17. Not from 4.0.17 to 4.1.7.

Viewing 3 posts - 1 through 3 (of 3 total)