-
Mdac
I have been having a problem with my VB(front)/Access(back) application...getting an error about E_Fail Status.
After searching the forum for answers, the only solid response I've found is, "Upgrade to MDAC 2.7 and this will solve the problem."
I have two questions...
1) I only get the E_Fail error when pulling records from one of 15 tables. The connection never changes, the table doesn't have anything particular about it. Does this make sense that the error would only occur with one table?
2) I am currently running MDAC 2.61. If I upgrade to MDAC 2.7, is it possible to revert back to 2.61? I've heard rumors about not being able to go backwards with MDAC, similar to DirectX.
Any help would be appreciated! Thanks in advance.
-
Q: I only get the E_Fail error when pulling records from one of 15 tables. The connection never changes, the table doesn't have anything particular about it. Does this make sense that the error would only occur with one table? No, it doesn't. Would it be feasible for you to delete the table, and then recreate and repopulate it?
Q: I am currently running MDAC 2.61. If I upgrade to MDAC 2.7, is it possible to revert back to 2.61? I've heard rumors about not being able to go backwards with MDAC, similar to DirectX. Quite frankly, I don't know because I've never tried to or had to. Would it be feasible to update the MDAC on one PC, and only one PC so you could run some tests?