Sage 100

 View Only

  • 1.  ODBC password stuck in VI job

    Posted 07-09-2019 17:22
    How does one change the ODBC data source password in a VI job?

    I can enter the new password in Import maintenance, read the tables etc... But when I go to run the job, it fails and shows the old password in the error message.

    What am I missing?

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------


  • 2.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:29
    Is the password hard-coded in the odbc driver?

    ------------------------------
    Doug Higgs
    Assistant Technical Support / Building Maintenance Specialist
    Midwest Commerce Solutions, Inc
    ------------------------------



  • 3.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:31
    @Doug Higgs yes, the password is in the ODBC.​

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 4.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:34
    Is your old password behind the green key?


    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 5.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:41
    @Kevin Moyes, no, I am entering the new password with the green key, then I can read the tables and browse records, but when I go to run the job I get the error.​

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 6.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:49
    The only other idea I have is that the DSN needs to be consistent between workstation and server.  I had an issue once where I was getting a password failed error, when the server DSN was different than the customer's terminal server DSN (...they moved a database to a new SQL instance but only updated one DSN).
    (Side note: brilliant security Sage, having your error message broadcast in plain text what the password is... simply brilliant design).

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 7.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:49
    Not sure what made it start working, but I launched from Job Select, tested it, got the failed message, went into Job Maintenance (from the import screen), saved the user and password again, accepted the job, and tried testing again and it worked!? It seems to have stuck this time, as I tried it again from the menu and it seems to be OK.

    So next question, the SQL Table owner has changed the structure (added columns) this ODBC points to, how do I pull in the new fields?

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


  • 8.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 17:59
    To pull in new fields, go into the table settings and remove / re-add the table, then verify the column order didn't change.  If you've manually edited the SQL (eg. sort order) then you'll have to put that back in place after re-adding the table.  You could probably add the fields by directly editing the SQL, but I use the remove / re-add method.

    ------------------------------
    Kevin Moyes
    Technical Systems Analyst
    Munjal White Consulting Co.
    Toronto ON
    ------------------------------

    Original Message


  • 9.  RE: ODBC password stuck in VI job

    Posted 07-09-2019 18:11
    Edited by Greg Stiles 07-09-2019 18:19
    @Kevin Moyes thanks! It was easier to add the columns to the SQL query. Would have had to setup the linked tables again.​

    [EDIT] Manually adding the columns to the SQL statement didn't actually work, the fields do not appear in the Data tab. Had to remove and re-add the table.

    Appreciate everyone's help!

    ------------------------------
    Greg Stiles
    S & W Microsystems
    Torrance CA
    310.787.1010
    ------------------------------

    Original Message


Related Content