• State Suggested Answer
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 64 subscribers
  • Views 2033 views
  • Users 0 members are here
Options

How do you get to the Data Source Settings dialog?

David. Alden

How do you get to the Data Source Settings dialog? (I want to process mdb files.)
I have the ODBC parser loaded, but I can't find any way to parse the mdb files.
Rate translation
×
Suggest better translation
×
  • 0
    You need to add new source as File Type > ODBC Databases then click Finish.
    This will display the Build Connection dialog where you need to build the Connection String:
    Use MS Office 15.0 Access Database and in the next tab add the physical location of the MDB files in the Data Source.
    E.g. C:\database.mdb
  • 0 in reply to Adrian Maniu
    That is what I tried, but the mdb files don't show as ODBC databases when I add a source. (And if just add one, the ODBC parser won't show as an option, even though it is loaded in Tools-Parsers list.)
  • 0 in reply to David. Alden

    When using the ODBC database parser, you cannot add the MDB as a source file. Databases don't need to be stored on your device. So the trick is to use the Add Source function, but then select ODBC Databases from the file type drop down list. Then click OK, without any selected file.

    After clicking on Build (connection string) in the upcoming dialog, I think that you need to use the Microsoft Jet 4.0 OLE DB Provider for MDB file. In this provider you can select the MDB file. If this is done and the connection string is tested you can click on the Setup button. This will bring up another dialog where you can select tables and columns to be localized.
  • 0 in reply to Achim Herrmann
    That worked well. Thank you.
    Now, however, I want to align the currently existing translations to get them into my Passolo project.
    After Creating/Updating the source and target lists, I get a correct set of source strings. When I try to Scan Target File, I get random target strings from the mdb file as the translations. (I don't see a unique key for the strings, and I can't set the source string as both a key and as the source text.) (The table has 5 fields: node_name, token, source text, language and target text. The are only 13 different node_names for the 9973 strings, and only 2 tokens. (Almost all tokens are = 0.))