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: Importing from Excel #14405
    soccerbum
    Member

    Access 2000 was able to take the Excel 2000 files and import them without much of a problem.

    From there, SQLyog was able to import the Access DB. My only problem now (being a SQL newbie) is taking the ID column I'd made for each table (workbook) in the spreadsheet and getting those IDs (int (4)) unique to be used as the primary key. Each workbook has 1-25, but of course if I'm putting them all as tables under a database (called, say, assets), they have to be unique. SQLyog pops up warnings for every single record, so I think my solution will be to make those columns a non-primary key before I import them into SQL, then use SQL to make the ID column in each table Primary (hopefully renumbering them for me in the process).

    Which is a different problem and in my opinion a step forward! 😆

    If the Excel ODBC worked properly would I need to fret over the similar ID column values? My brain locks up at that point. 😮

    In any case, thanks for the Access workaround (and the OpenOffice one too!). I can stumble onward now…

    Chris

    in reply to: Importing from Excel #14403
    soccerbum
    Member

    Ok, I'll see if I can wrangle a copy of Access from somewhere and try that route.

    If it's an ODBC thing, does that mean I'm SOL?

    Is this important enough to get some personal verification from the SQLYog authors? What do ya think?

    Thanks for the ideas! 😀

    Chris

    in reply to: Importing from Excel #14398
    soccerbum
    Member

    Modifying my 'Edit MySQL' input with this:

    create table `assets`.`engineering` (

    `id` int (4) AUTO_INCREMENT,

    `Device` varchar (255) NULL ,

    `Make` varchar (255) NULL ,

    `Model` varchar (255) NULL ,

    `Includes` varchar (255) NULL ,

    `Serial` varchar (255) NULL ,

    `DatePurchased` varchar (255) NULL ,

    `Vendor` varchar (255) NULL ,

    `Cost` numeric (19,4) NULL ,

    `Invoice ` double (15,0) NULL ,

    `Location` varchar (255) NULL ,

    `F11` varchar (255) NULL,

    PRIMARY KEY (id)

    );

    I still get the same error. 🙁

    Thanks for the suggestion though. I forgot about the primary key and would have had to enter it later had you not spotted it.

    Oh! I had forgotten to add that when I hit the 'Run Immediately' button, I get a dialog box about losing connection to the database. However, every time I refresh anything it connects back up with no problem, so I was under the impression it's connecting (again) fine and wasn't part of the problem here. I just mention it here for thoroughness.

    Anything else?

    Cheers,

    Chris

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