Bug #1876 | MyODBC 3.51.06 Bug | ||
---|---|---|---|
Submitted: | 18 Nov 2003 10:48 | Modified: | 28 Nov 2003 9:48 |
Reporter: | Justin Kent | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.06 | OS: | Windows (Windows XP Home/Pro) |
Assigned to: | CPU Architecture: | Any |
[18 Nov 2003 10:48]
Justin Kent
[28 Nov 2003 9:48]
Dean Ellis
I cannot repeat this issue with MyODBC 3.51.06 and MDAC 2.7 or MDAC 2.8 using the basic code sample you have provided, in either VBA/Word or VB itself. Unless there is something more substantial in the code which was not included in your example, I can only assume that whatever the problem may be, it is not the fault of MyODBC, as MyODBC itself of course does not care whether or not your code uses an IF statement. Thank you
[1 Dec 2003 1:57]
Justin Kent
Thank you for your response. I understand that you cannot replicate the error. I have now loaded the same macros onto different operating systems and still the error occurs. I am therefore stumped! Literally, the only difference between the macros working and failing at the points outlined in my previous message is on which MyODBC driver I use. The v2.5 works fine but the v3.51 fails. I have rolled back to the previous driver and guess I will have to continue with that one. Justin Kent.