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

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 36 total)
  • Author
    Posts
  • in reply to: Error importing in v3.6 RC5 #15053
    Hughes
    Member

    Maybe I'm using it improperly. In my test, I changed a single value in a column, committed it, and then ran the sync tool. Should it detect the difference between the two tables?

    Also, what's the word on the column truncate problem. The check box does not work.

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

    Attached is a single script that contains the CREATE statements for both tables. I trust this is what you're looking for in your previous request.

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

    I'm feeling the pressure now. 🙂

    I'll get you the other half tonight. BTW, what am I getting paid for my testing services? 😉

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

    I'm going reply-crazy this morning! 😉

    Another bug:

    If I perform an export table as batch script and then perform a second export, the file is overwritten. I am not prompted to rename the file as was stated earlier in the post.

    in reply to: Error importing in v3.6 RC5 #15046
    Hughes
    Member
    Ritesh wrote on Oct 8 2003, 01:53 AM:
    BTW, are you sure that the order of COLUMN in the PRIMARY KEY definition are same?

    Yes, the PK value is the same.

    Attached is the create table script. Please let me know when you have it so I can remove it.

    Also, if you need a video on this one, let me know.

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

    Another bug:

    1. I have “Truncate columns to max data size” preference unchecked. However, when I execute my query, the column widths are not adjusting to the size of the column name (as it did in previous versions). See graphic below for details.

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

    I'll get to it tonight.

    What about the other bug I documented?

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

    Bad news. Found some more bugs:

    1. If you enter a value in Export to File field on the Export Data window, the value persists after you have closed the window. This parameter should be cleared out (as it was in prior versions) since you don't want people accidentally overwriting a prior export file.

    2. The DB synch does not appear to be working. I created an exact copy of a table in my current DB and then created a new DB that contained that table. I then updated a single record in the current DB. When I went to synch the two DBs, it issued an error msg stating that no differences between the tables could be found. Shadow…can you back me up on this one?

    The ball is back in your court. Happy bug hunting. 😉

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

    I haven't tried it yet. However, I do have a pair of DBs that need synching. I'll take it for a test drive tonight and post my thoughts later.

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

    Ritesh…I have confirmed this is working now. Thanks!

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

    The “Terminated By” for fields value, by default, is set to NONE, Terminated By for Lines is set to NONE, and the ESCAPED by value is set to NONE. The default settings should be set up as it was in its predecessor:

    • Terminated By (fields): t
    • Terminated By (lines): n
    • Escaped by: \

    Currently, by default, import and export is broken. I have confirmed this continues to be a defect in RC6.

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

    Ritesh…there's definitely a bug here. A default export to CSV and then a corresponding import results in an error (detailed in Shadow's response).

    I'll double-check the error that I saw when I get home tonight. The one thing I know for certain is that the CSV file generated in v3.52 looks different than the file in v3.6 RC5 when opened in Edit Plus (a notepad hybrid).

    *By the way, thanks for the UI tip. I've got everything looking like the prior version now.

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

    Yes, I meant to say CSV file, not a batch file.

    Based upon your comment, are you acknowledging the bug?

    in reply to: Comments on v3.6 Release Candidate #15009
    Hughes
    Member

    Ritesh..

    This is odd. My email bounced back with the following msg:

    Your message was not delivered because the destination computer refused

    to accept it (the error message is reproduced below). This type of error

    is usually due to a mis-configured account or mail delivery system on the

    destination computer; however, it could be caused by your message since

    some mail systems refuse messages with invalid header information, or if

    they are too large.

    Your message was rejected by inbound.registeredsite.com for the following reason:

    5.7.1 This mail message is infected by I-Worm.Swen

    I ran a full virus scan and I don't have this (or any) virus. Regardless, since it appears email is not an option at this time, I have uploaded the file to the following location:

    http://www.askthecommish.com/webyog/webyog.zip

    Please let me know when you've downloaded the file so I can remove it. Thanks!

    in reply to: Comments on v3.6 Release Candidate #15008
    Hughes
    Member

    Ritesh…I have sent the movie file. Its 760kb and stored in a Flash (.swf) file. It details the problem perfectly.

Viewing 15 posts - 16 through 30 (of 36 total)