Problem Using BOL example for using ODBC to import instead of Bulk Edit

I'm working through the example for using ODBC and Access instead of the Excel Bulk Edit utility and am running into a problem with the BOL example. It has you start by building a module template and then using that to create the format specification, so far so good. The problem occurs when I get to setting up the Access database. Step 6 says "The number of fields required in the table equals the number of is_a_string_parameter  fields in the module's format file. There are 43 is_a_string_parameter  fields in the example's TEMPS.FMT file." but when I look at the TEMPS.FMT in a text editor I have 101 fields identified and most of them have an "F" instead of a "T" which I am guessing means that those aren't string parameters. So first question is does the "F" mean that the parameter isn't a string? Second question is why am I coming up with so many more parameters than the BOL example since I used the directions on setting up the format from BOL?  It's hard for me to imagine that things like the alarm help data aren't strings while the AI1/HI_LIM.CV is so either I don't understand the meaning of the "is_a_string_parameter" flag or an awful lot of things I'd expect to be strings aren't.

5 Replies

  • Bruce,

    I would just export some sample module data using your format file and then take this generated text file and import into your Access database and create a table.

    This should have the fields formatted correctly in the access table and then you can remove the data just leaving the table with the format.

    Just as a FYI, we have recently found an issue with using ODBC as an import source in v11.3 and at this point it is still an open call (AC-1301-1791).

    Regards,

    Matt

  • In reply to Matt Stoner:

    Haven't tried that approach but will to see what happens, thanks. Please keep me posted on the open call as I'd really like to be able to use ODBC rather than the Excel bulk edit.

  • In reply to Bruce Brandt:

    OK now I've tried that and get the same message about not having enough fields. Very non-intuitive that a database created from an export doesn't have the right number of fields for a subsequent export.

  • Hi Bruce  ...  Don Dahlman
    /wave


    On Tuesday, December 17, 2013 11:55 AM, Bruce Brandt <bounce-Bruce_Brandt@community.emerson.com> wrote:
    OK now I've tried that and get the same message about not having enough fields. Very non-intuitive that a database created from an export doesn't have the right number of fields for a subsequent export.
  • In reply to asterof:

    Hi Don, how's things?