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

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 36 total)
  • Author
    Posts
  • in reply to: Main window not appearing all of a sudden #16263
    Hughes
    Member

    Version 3.63.

    in reply to: Main window not appearing all of a sudden #16261
    Hughes
    Member

    LOL. I just figured it out.

    For some reason, these values in the INI file were all negative:

    Left=-32000

    Top=-32000

    Right=-31840

    Bottom=-31966

    The software should prevent this from happening since it forces the window off of the viewable area. The top and left values should always be set to 0 when the app starts up. Hopefully this has already been fixed in a later release.

    in reply to: Main window not appearing all of a sudden #16260
    Hughes
    Member

    I played around with it a little more and it appears as though the problem is tied to the SQLyog.ini file. I found this out after I overwrote the ini file of a slightly later version of SQLYog and the same problem occurs. Any thoughts?

    in reply to: Cannot update fields in v3.62 #15243
    Hughes
    Member

    Ritesh….any updates on this defect?

    in reply to: Cannot update fields in v3.62 #15242
    Hughes
    Member

    Ritesh, I have emailed you the script to rebuild the table. I haven't had time to create a video, but if you follow the directions in the email, the problem is easily recognized.

    in reply to: Cannot update fields in v3.62 #15238
    Hughes
    Member

    I am using v3.62 and version 4.0 of mySQL. Here is what is in the history:

    [6:58:38 AM][ 47 ms] use `MYDATABASENAME`

    [6:58:38 AM][ 47 ms] use “

    [6:58:39 AM][ 78 ms] show tables from `MYDATABASENAME`

    [6:58:58 AM][ 47 ms] select database()

    [6:58:58 AM][ 63 ms] show tables from `MYDATABASENAME`

    [6:58:58 AM][ 46 ms] show fields from `MYDATABASENAME`.`MYTABLENAME`

    [6:58:58 AM][ 47 ms] show fields from `MYDATABASENAME`.`MYTABLENAME`

    [6:59:07 AM][ 47 ms] select database()

    [6:59:07 AM][ 62 ms] select * from MYTABLENAME where week_num=11

    [6:59:07 AM][ 63 ms] show tables from `MYDATABASENAME`

    [6:59:08 AM][ 47 ms] show fields from `MYDATABASENAME`.`MYTABLENAME`

    [6:59:08 AM][ 47 ms] show fields from `MYDATABASENAME`.`MYTABLENAME`

    [6:59:39 AM][ 62 ms] select * from MYTABLENAME where week_num=11

    Following the exact same procedure in v3.61, the history includes an update command. As always, if Ritesh and co. need an mpeg of the problem, please let me know.

    in reply to: Error importing in v3.6 RC5 #15072
    Hughes
    Member

    Here is a screen grab to demonstrate what I'm talking about:

    in reply to: Error importing in v3.6 RC5 #15071
    Hughes
    Member

    RC8 is very nice. The updated icons look GREAT. I did find one bug that was previously fixed:

    The default settings for exporting have been reset to NONE. It should be:

    • Terminated By (fields): t
    • Terminated By (lines): n
    • Escaped by: \
    in reply to: Error importing in v3.6 RC5 #15068
    Hughes
    Member

    I concur with Shadow. My sja.log file is stored to my Desktop. I have the shortcut to SQLYog stored there.

    in reply to: Remember table info on ODBC import? #15084
    Hughes
    Member

    Now that I've figured out how to use the sync, I agree. This feature would be very helpful.

    in reply to: Error importing in v3.6 RC5 #15063
    Hughes
    Member

    Sorry about that. I'm new to the sync features. However, now that I've used it, I love it!

    Do you have an ETA for the next RC release?

    in reply to: Error importing in v3.6 RC5 #15061
    Hughes
    Member

    When I run it using the wizard, everything works! But that leaves me with a question: What is the purpose of that screen I showed in the video? Should it result in the same results?

    in reply to: Error importing in v3.6 RC5 #15059
    Hughes
    Member

    Sorry about the truncating thing…its been a long week for me.

    At any rate, no log file is created. Worth noting is that I still have previous versions of the software on my PC (but installed in a different directory). Here is my screen capture:

    in reply to: Error importing in v3.6 RC5 #15057
    Hughes
    Member

    For your viewing pleasure.

    Also, can you please give me a heads up on the truncating problem?

    in reply to: Error importing in v3.6 RC5 #15055
    Hughes
    Member

    I'd love to. Unfortunately, I cannot locate the sja.log file. Its not in the SQLYog folder.

Viewing 15 posts - 1 through 15 (of 36 total)