> The small demo script below makes ADO calls to a Microsoft > Access (Jet) > database via win32com. But it fails in a potentially dangerous way; > "SELECT int * int;" can return None with no warning if the result is > large enough. This can also occur if one or both of the operands is a > column reference. > > The same SQL run as a Query inside the Access GUI works as expected. > Manually changing one of the ints to a Single by appending > ".0" works as > expected. > > Any ideas about where I need to look next to find the cause > of, and then > fix, this behavior?
I'd suggest using VB to see if the behaviour is different than with Python. If it is and we can narrow a test case to a very small snippet, then we can probably sort out why. If VB works the same, it is likely to be a "feature" of ADO as implemented, and not much we can do. Cheers, Mark
<<attachment: winmail.dat>>
_______________________________________________ Python-win32 mailing list Python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
