Google SitemapAdmin

[Woodymon]

Woodymon

Thanks for the help. I couldn't delete the entries using the uninstall.sql file - said it couldn't find the configuration_groups table. So I used phpMyAdmin and (taking a deep breath and closing my eyes, crossing my fingers, stroking my lucky rabbit's foot etc.) deleted the entries in the relevant tables and then used the install patches just to run the install.sql file. I realised that I had previously also run all of the update sql files, hence, presumably, the duplication.

It is likely you have a prefix (e.g. zen_) on your db tablenames and thus uploading the uninstall.sql through Zen Cart's sqlpatch tool did not work for you. In these cases try pasting the sql code into the sqlpatch tool edit box.

It's strange that you would have duplicate entries (table records) with the exact same parameters (fields) in your related db tables. When running a SQL statement which would duplicate pre-existing records in a table, by default MySQL should report back the record already exists, and not update the table with those particular records.

But if doubt and you are having issues (and you know what you are doing) phpmyadmin is the way to go.

Woody

[blag]

It is likely you have a prefix (e.g. zen_) on your db tablenames and thus uploading the uninstall.sql through Zen Cart's sqlpatch tool did not work for you. In these cases try pasting the sql code into the sqlpatch tool edit box.

It's strange that you would have duplicate entries (table records) with the exact same parameters (fields) in your related db tables. When running a SQL statement which would duplicate pre-existing records in a table, by default MySQL should report back the record already exists, and not update the table with those particular records.

But if doubt and you are having issues (and you know what you are doing) phpmyadmin is the way to go.

Woody

Woodymon

I tried using the sqlpatch tool, and that reported errors about missing tables: it even reported the correct database name, prefix and table, but reported the table as missing. In fact as far as I coul tell all was correct, but sql patch wasn't happy about something!!!