Thanks, I'll try that.
I realized I had a product in the cart. I removed and ran update again and cut it down to just one error message.

user warning: Table 'refineda_drpl1.uc_flatrate_methods' doesn't exist query: SELECT mid, title, label FROM uc_flatrate_methods in /home/refineda/public_html/includes/database.mysql.inc on line 172.

I'll try the reinstall.

Thank, torgosPizza

It would not be good to edit line 172 as it is an error routine:

if ($debug) {
print 'query: '. $query .'error:'. mysql_error($active_db) .'';
}

if (!mysql_errno($active_db)) {
return $result;
}
else {
trigger_error(check_plain(mysql_error($active_db) ."\nquery: ". $query), E_USER_WARNING);
return FALSE;
}
}

The trigger_error is line 172.

Hello Ryan,

Essentially, the install file had a case install statement to create the uc_flatrate_methods db table. The case statement had nothing in the case of "mysql," and the case below showed the create db in the "mysqli" case. Since there was no break, the "mysql" case should have dropped to the "mysqli'case and the db created. It was not. I looked for some sort of code error, but did not see anything in the include file.

I looked through the rest of the include and saw the uc_flatrate_method was used a lot.

What I did was manually create the uc_flatrate_methods table in the db through the php db administrator on the server site, as described in the include file. Then ran update.php and the problem disappeared.

Don't know why the db was not created, but the manual creation seemed to fix the problem.

Dale

That's good information. I did notice that the uc_flatrate_method table was indeed not present in the older version.

However, I had uc_flatrate enabled when I did the initial update, the initial update.php, and got the error.

It turned out I had an item in the cart. I do not know think that mattered. After the error appeared, I disabled the uc_flatrate in workflow_ng, but did not disable the module, and took out the product from the cart, and ran update.php again, but got the same error.

This may seem at odds with what you said above, but I believe that the cache had something to do with showing the error when it may have been corrected. I had to delete the cache, via the drupal developer module to get the error out of my browser. And I also repaired the MySQL db on the server, when after creating the table manually it did not show up in the db structure. Now, everything seems ok.

So your explanation may be correct. I can't say since I'm not sure if the browser was telling current info after I ran update.php, or whether the db structure was there until I did the db repair.

I think your suggestion of running update.php when you enable a new module is a good suggestion, and something I'll include in my bag of tricks. Thanks.