Is it possible there is some bad data in the larger db? This is asinine, but maybe write a small script that adds some data, then opens and closes the db, then repeats this. If this is a size issue, then you can at least narrow it down to where the size limit is? And, if it isn't you should be able to figure that out, too. Otherwise, play around with the locking and cursor options.
-d "Gyula" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Hi there, > > I have been running Python to tap into an MS Access 2003 database > using ADO (PythonWin+COM). Everything works great creating recordsets > etc. when I open a table with a small number of records. However, when > I try to run the same Python code with a large table (>100,000) I get: > > Traceback (most recent call last): > File "C:\Python25\Lib\site-packages\pythonwin\pywin\framework > \scriptutils.py", line 310, in RunScript > exec codeObject in __main__.__dict__ > File "C:\Documents and Settings\user\Desktop\PythonWS\scripts > \readmsaccess.py", line 43, in <module> > rs.Open('SELECT * FROM ' + tblname, oConn, 1, 3) > File "C:\Python25\lib\site-packages\win32com\gen_py\2A75196C- > D9EB-4129-B803-931327F72D5Cx0x2x8.py", line 2364, in Open > , ActiveConnection, CursorType, LockType, Options) > com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, > 5003251, -2147467259), None) > > The small and large table structures are identical, all I do is change > the tblname from input1000 (1000 records) to input (>100000 records). > I use optimistic locking and keyset cursor..nothing out of the > ordinary? > > Any ideas? ADO 2.8 is what I am using. > > Thanks a lot! > GG -- http://mail.python.org/mailman/listinfo/python-list
