Originally Posted by MikeV
I do have a separate db for calendar and mambo and re-created the db for calendar a couple of times.
That is your problem... I'm going to try to explain it in simple terms... Everytime you use a script that connects to a database, you have to specify which database to use (not you, but the script does it). It does so by issuing the "USE mambos_database;" call to the mysql server. It then goes on doing several "SELECT * from some_table;" to fetch its data...
Now lets use that in this situation... You have Mambo (which is a script if you will), and EPC (which is another). Since they can both be run independantly, they each have to do the "USE some_database;" call at the begining... So here's what happens when you get to Mambo's front page...
Mambo does its includes
One of the includes does the initial database connection "USE mambo_database;"
Mambo does a few "SELECTS ..." to get some content and blocks
OH! One of the blocks is EPC
EPC does its includes
EPC initiates its database connection "USE epc_database;"
EPC does the "SELECTS ..." to get the events information
EPC completes and says "I'm done, Mambo... you can keep going"
Mambo then tries to do a "SELECT * FROM some_table" to feed a block
MySQL says "I don't see some_table in the epc_database" and Mambo craps out.
As you can see, in the blocks after the calendar, the MySQL is still using the "USE epc_database;" call that it last received and MySQL doesn't find the tables that the SELECTs are looking for... You can see it in your error message...
Table 'calliopy_ecalendar.mos_poll_menu' doesn't exist
calliopy_ecalendar must be the database name you have for the calendar... and mos_poll_menu is a table that you should find in your Mambo database.
If you absolutely can't put EPC's table in the same database as Mambo, your only solution would be to run with the flatfile. If there is no issue with you adding another table to Mambo's database, it should be fairly easy to move the table from one DB to the other.