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: Automated Access Import Of Linked Tables #20256
    jbergholm
    Member

    thanks for all your help in researching this, peter. as i mentioned, i could not use comma-delimited .csv files but used instead tab-delimited and was never able to make that work with the migration tool. it kept telling me that error that i attached last time…something about not being able to read [null] into [null]. on trying a different file (this would have been a monthly output of sales data) i'd get thru the defining of the format in ODBC but when i get to the point (in the migration tool) of choosing the file i had used to define the format (in the ODBC administrator) it would tell me that no data was being returned from that particular file. so if i attempted to run it on one of the other monthly dumps i was't getting all my fields…only three out of about 15 showed up as F1, F2, F3 and then when i pressed forward and ran it any ways it erred out saying there was an invalid F1 key in the first field.

    seems like it should have been a straight forward process. i suspect it's a data issue in the underlying .csv table.

    my whole intention was so get dumps from quickbooks so i could do sales reports in crysal reports that i was unable to do directly in QB. in the end i've found an easier if more expensive solution. A $150US ODBC driver that allows me to ready the Quickbook tables directly without all this output and transformation…duh! why didn't i think of this before?!

    again, thanks for all your help.

    -john-

    in reply to: Automated Access Import Of Linked Tables #20253
    jbergholm
    Member

    peter, from the link you sent me earlier, i found this:

    2) Consider using ODBC instead. For instance an Excel data file (.xls -file) can be opened from Microsoft Access as a 'datalink' and you can transfer data using ODBC. Then you even don't have to define the columns in advance if the spreadsheet contains the column names in the upper row. ODBC does that for you. And with the SQLyog ODBC/Migration tool you can adjust the datatypes to your need in the import proces.

    this is exactly what i was trying to do but have so far been unable to “see” linked tables in access. any suggestion?

    in reply to: Automated Access Import Of Linked Tables #20252
    jbergholm
    Member

    peter, thanks for your quick reply. you suggestion is pretty much what i tried first, except that i made it a tab-delimited .csv file due to the fact that one of the columns holds product descriptions which contain commas. i'll give the semicolon delimiter a try.

    -j-

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