Close This Window

Invalid Column & Running UpdateDB2

SITUATION

I get the error :

"The Microsoft(tm) ODBC connection experienced the following error:
Invalid object name 'pharmacies'.
Statement(s) could not be prepared.

Location - GetListOfPharmacies #0"

This error is caused from missing columns in the database.  It could say several different Objects names I just used "pharmacies" as an example.  When bring out a new versions we often times add columns to the database and sometimes they don't get updated during an installation.

SOLUTION

To correct this problem we just run our utility called "UpdateDB2".  But first we need to make sure we are running the most current Version of the utility. 

1.To do this please go to add/remove programs and remove any old versions of SOAPware that exists.  WARNING if this is the server and your still on access databases this will erase your data please make a backup first. 

2. Once older versions are removed we need to repair the new versions so it will rebuild the latest version of all the files we need.  So click on the "Change/Remove" button for the latest version but this time instead of removing it check the bullet that says "Repair".  Now that we have the latest version of UpdateDB2 its time to run it.

3. Go to My computer then click on Local disk C:-->SOAPware-->New DB's.  In here you will run the program called UPDATEDB2.
    *If you recieved an error when running UpdateDB2 please see the next section titled
      "I Received an Error during UpdateDb2".

Once this is complete You should not receive these errors again.  If you do there maybe something further wrong with your data and you need to contact us at 800-455-7627 ext 300.

*I Received an error during UpdateDb2.

I received the error "CEATE TABLE permission denied in database 'master'" when running updatedb2.  This can be caused by 2 things but both are related to your ODBC settings.

1. The DSN(Data Source Name) may not be mapped to the correct database.  To check this we will go
   to the ODBC.
    a. Click Start-->Run now type "ODBCAD32" and Click OK.  This will take you to the ODBC.
    b. Once in the ODBC click on the "System DSN" tab and we'll start with SW Charts DSN.
        Your screen should look something like this:

      

    c. Now we will Double Click on the SW Charts DSN.  Now your screen should look like this:

       
   

    d. Click Next.  Now you should see the login information screen.  Make sure the box for
        "SQL Server Authentication" is checked.  You will use either "sa" with a blank password or
        "soapuser" and "soapware" as the password.  Your screen should now look like this:

   
       

    e.  Click Next to login.  Now this screen is where the problem will be.  What will be wrong is the
        check box at top of the screen will not be checked or the Default Database will be mapped to
        the wrong database.  In this example we were using SW Charts so the default database should be
        sw_charts.  You'll notice in the next image that the check box is unchecked which means it defaults
        to the master database and that's what's causing the error. You'll want to Map the Corresponding
        database with each DSN.  So you'll need to check all 6 DSN's to make sure they are all mapped to their
        correct database.

       

2.  Another possibility is that there is a remnant of the old DSN's still in the registry.  To check this we will go
    to the registry.
    a. Click Start-->Run  then type "Regedit" and hit OK.
    b. Now we will browse to this location:
        HKEY_CURRENT_USER-->Software-->ODBC-->ODBC.INI
        Under here you will see several folders.  Do not delete any folder unless it starts with SW because
        they are folders that are created by windows and have nothing to do with SOAPware and could harm
        your computer.
    c. You need to Delete all the folders that start with SW for example "SW CODES", "SW Charts",
        "SW Exchange", "SW Images", "SW Transactions" or "SW Users" but exclude
        the 2 folders that say "SW Mover" and "SW DBCompare" those 2 are supposed to be there.

Now you should be able to run UpdateDB2 with now problems.  If problems still persist please call us at 800-455-7627 ext 300.

 

Close This Window

The information provided in the SOAPware, Inc. Knowledge Base is provided "as is" without warranty of any kind. SOAPware, Inc. disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall SOAPware, Inc. or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if SOAPware, Inc. or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.