Last night we upgraded to MOM version 6. I came in this morning to find that none of our intranet MOM reports were functioning properly... or at all.
Nothing works. Output was stated as:
Microsoft OLE DB Provider for ODBC Drivers error '80040e37' [Microsoft][ODBC Visual FoxPro Driver]Not a table. ...File Path and Line Number of error...
Based on the information that I had accessible from MOM 5.4 table structure, I took a look at the table structure of MOM version 6 only to find all of the essential fields still there with some more included (obviously, since MOM version 6 has a good number of additional features)
DSN Connection using the live MOM DBF files has always worked well for us in the past, since infomration could be gathered in real time.
I guess my question has two parts.
- Why doesn't ASP think that the tables that I am querying (the ones that worked yesterday) are tables? Did Dydacomp do something differently besides update them?
- It also gives an error code of '80040e37', as stated above. Can someone explain to the best of their knowledge what it means?