Need help...possibly in over my head w/Access & .asp

[chrisman]

I'm working on a website that was designed by a design company who has since been bought out by another company which has been taken over by another company. The client has hired me to fix some of the problems with their website that the company has not taken care of.

I need some help figuring this thing out. Here's the description as best as I can understand it:

The website has an Administration website within the main website. This Administration tool is used to add/remove/edit those areas of the website that constantly change (jobs, calendar, scrolling headlines, etc.) Right now I'm working on the Calendar. The Administration portion works great. I can login, add a new event, it gets written to the Access database and all is well. The problem is with the main website calendar that is (I assume) supposed to display the events written to the database. The calendar STARTS to display correctly (prev month, next month, prev year, next year) and shows the day of the week: M T W Th F S S but then stops as it starts to display the numeric days of the month (

http://www.cityofgreenriver.org/cal/eventcal.asp)

and displays this error:

Microsoft OLE DB Provider for ODBC Drivers
error '80040e37'

[Microsoft][ODBC Microsoft Access Driver] The Microsoft
Jet database engine cannot find the input table or
query 'ev_event'. Make sure it exists and that its name
is spelled correctly.

/cal/calendar_utils.asp, line 76

Here's the kicker, it doesn't appear that the table 'ev_event' exists ANYWHERE within the database.

Can anyone help me out? I can provide access to the files necessary (at least the code) and would even call someone that could walk through this thing with me.

Thanks so much!

 

[abcorwin]

chrisman,

The error message indicates that the problem is in the data collection rather than in a problem with the display of the calendar.

Identify the query that is being called either by stopping the execution in the debugger (preferred) or having the system display a message containing the query text. Compare this against your database to make sure that it is asking for entities that actually exist. If not, the problem is in the code that created the query (most likely), but this may be a trickier problem if all of the entities exist. Remember when checking that Access uses the same namespace for tables and queries.

Hope that helps.